Andy Race

You can create feature specifications from natural language, clarify ambiguous requirements, generate implementation plans and dependency-ordered tasks, execute those tasks, run cross-artifact consistency analysis across spec.md, plan.md, and tasks.md, and convert tasks into GitHub issues.

Software architects, engineering leads, and developers practicing specification-driven development benefit most. They suit teams that want structured feature specs, planning artifacts, and traceable task breakdowns before writing code, such as architecture groups like Aurora Insurance's engineering organization.

Every skill requires an existing spec-kit project structure containing a .specify/ directory. The skills operate on spec-kit artifacts such as spec.md, plan.md, and tasks.md, so the project must already be initialized with the github-spec-kit template layout before invocation.

Start with speckit-specify to draft the spec, use speckit-clarify to resolve gaps, then speckit-plan and speckit-tasks to produce design artifacts and ordered tasks. Run speckit-analyze for consistency checks, speckit-implement to execute, speckit-converge to capture remaining work, and speckit-taskstoissues for GitHub tracking.

The skills are published publicly on the AndyRace GitHub profile and are derived from the github-spec-kit project templates, as stated in each skill's metadata. No licensing fee or paid tier is indicated in the manifest; they are freely accessible in the public registry.