development-advanced

Consumes a Sprint Plan slice (one epic or feature) + the governing ADR Y-statement + a Spec slice, and produces ticket design — Write-set, dependencies, acceptance criteria, and complexity — for AI-ready tickets. Owns per-cycle design; writes NO design-doc file. <example> Context: /sprint-tickets assigns each epic to a separate code-architect agent in parallel user: Create tickets for the auth login sequence epic agent: Reads the Sprint Plan slice, the touched-module Spec sections, and the governing ADR Y-statement, then produces ticket-sized units with a Write-set, dependencies, acceptance criteria, and US-### back-refs </example> <example> Context: /sprint-tickets needs detailed implementation design for a complex feature user: Design the environment checking system from the Sprint Plan agent: Identifies natural ticket boundaries, maps the Write-set and depends-on graph, and produces S/M/L complexity estimates for each unit of work — returning the design in findings, not a file </example>

Reviews PR diffs for bugs, logic errors, missing error handling, and pattern violations. Always runs on every review. <example> Context: /sprint-review always dispatches this agent as the core quality gate user: Review PR #42 agent: Scans the diff for null access, race conditions, missing error handling, and pattern violations, reporting each with file:line evidence and fix suggestions </example> <example> Context: A PR adds async code with potential unhandled rejections user: Review this PR that adds the install orchestrator agent: Finds a fire-and-forget async call missing await and an overly broad catch block, reports both with impact analysis </example>

Finds opportunities to simplify code without changing behavior. Reduces nesting, eliminates redundancy, improves readability. Always runs, in parallel with other reviewers. <example> Context: /sprint-review dispatches this agent in the parallel specialist batch user: Review PR #42 agent: Finds a 4-level nested conditional that can be flattened with early returns, and a wrapper function that just passes arguments through unchanged </example> <example> Context: A PR adds verbose async handling that could be simplified user: Review this PR that adds the auth login sequence agent: Identifies callback nesting that could use async/await and three duplicate error formatting blocks that should be a shared helper </example>

Explores a specific aspect of the project's codebase — architecture, patterns, or integration points. Reports findings back to the main model for synthesis. <example> Context: /sprint-plan needs to understand how the project is structured before writing a Sprint Plan user: Plan a new notifications feature agent: Explores module boundaries, entry points, and existing UI/data patterns, then reports file paths and architectural findings </example> <example> Context: /sprint-tickets re-explores the codebase after reading the Sprint Plan to gather fresh implementation context user: Create tickets from the latest Sprint Plan agent: Explores relevant modules and patterns so code-architect agents have accurate codebase context for designing tickets </example>

Checks whether code comments match the actual code. Finds comment rot, misleading docs, and outdated explanations. Runs when changed files contain code comments. <example> Context: /sprint-review detects that changed files contain JSDoc or inline comments user: Review PR #42 agent: Compares each comment in the diff against the actual code behavior, flagging stale parameter descriptions and misleading algorithm explanations </example> <example> Context: A function was refactored but its doc comment still describes the old behavior user: Review this PR that refactors the auth flow agent: Finds that the @returns annotation says 'token string' but the function now returns a Result object, and flags the mismatch </example>

Implement GitHub Issue tickets with wave-based parallel execution, subagent dispatch, lightweight review, and PR creation. Use when user has GitHub issues ready, says 'start coding', 'implement this', 'build the tickets', 'start building', or has open tickets that need implementation.

Create a Sprint Plan (the cycle-versioned objective), capture ADRs, write or update the living Brief and Stories, and patch the system Spec through guided discovery, codebase exploration, and architecture discussion. Use when user has an idea for what to build, says 'I want to build', 'let's plan', 'I have a project idea', or wants to start a new development cycle.

Fix review findings and update the system spec (.spec/spec.md). Sprint-aware — auto-detects a stack of PRs and fixes the whole sprint on the tip in one pass. Use when user has review comments on a PR (or a stack of PRs from one sprint), says 'fix these', 'address the review', 'refine my code', 'refine the sprint', 'update the spec', 'sync the spec', 'close out this cycle', or wants to finalize work after /sprint-review.

Review a PR with specialist agents and confidence scoring — surfaces only high-confidence findings. Sprint-aware — auto-detects a stack of PRs and reviews every wave so none is skipped. Use when user has a PR ready (or a stack of PRs from one sprint), says 'review my code', 'check this PR', 'review the sprint', 'is this ready', 'code review', or has an open pull request that needs specialist review.

Turn an approved Sprint Plan into AI-ready GitHub Issues with implementation detail and parallel wave analysis. Use when user has an approved Sprint Plan, says 'break this down', 'create issues', 'make tickets', 'turn this into tasks', or has a completed Sprint Plan that needs implementation planning.