RacingData

Fully implement a PRD's issues in dependency order — parallel worktrees, each merged to main as it passes, HITL issues left for a human. Use after write-a-prd + prd-to-issues, when the user wants to "implement the PRD", run the whole issue queue, or run /implementation.

Audit comments across the C# and Python codebase against the comment policy in AGENTS.md, then remove or rewrite the ones that don't earn their place. Use when the user wants to clean up comments, reassess comment value, prune redundant comments, or enforce the comment policy. Optional arg scopes the review — a path (e.g. RaceDataDownloader/), "changed" (git-modified files), or "staged".

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Verify all issues related to the current PRD have been completed and then delete all issues and the PRD itself to maintain a clean project management environment. Use when user explicitly states "clean up PRD" or when a PRD has been marked as completed and needs to be archived.

Pick the next AFK issue from issues/ and implement it end-to-end via TDD, then commit. Use when the user wants to advance the ralph queue, asks to "work on the next issue", or runs this in a /loop.

Review the AGENTS.md file to ensure all rules are up-to-date, removing any redundant or overly vague rules and updating deterministic guardrails as needed.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.

Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.