gsd-cleanup

Add tests to a completed development phase using its records and implementation. Review the proposed coverage, then generate unit tests for individual components and browser tests for full workflows, verify them, and commit the test files.

• Adding automated tests after a development phase is complete
• Turning acceptance criteria into test coverage
• Reviewing which code needs unit or browser tests

Prepare an AI-SPEC.md design agreement for an AI development phase. The skill coordinates framework selection, documentation and domain research, and evaluation planning so the phase has a defined technical direction and assessment strategy.

• Define the design agreement for an AI development phase
• Research frameworks, documentation, and the application domain
• Plan how to evaluate an AI system

Run an audit, separate findings that can be fixed automatically from those needing manual work, and apply eligible fixes with tests and separate commits. Use severity filters, a finding limit, or a classification-only dry run.

• Fixing audit findings with test verification
• Prioritizing findings by severity
• Limiting how many findings are fixed

Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.

• Checking completion criteria before archiving a milestone
• Reviewing coverage of milestone requirements
• Checking connections and user flows across phases

Audit acceptance tests, which check whether features meet user needs, and verification records across project phases. Compare outstanding items with the codebase, flag outdated documentation, and produce a prioritized plan for human testing.

• Finding outstanding acceptance tests across phases
• Collecting blocked items and checks needing human input
• Checking whether verification records match the code

Run remaining GSD project phases through discussion, planning, and execution, while recording progress and phase documents. You can limit the phase range or keep decisions interactive; after all phases finish, the workflow audits and closes the milestone.

• Running all remaining milestone phases
• Executing a selected phase or range of phases
• Answering discussion questions before background execution