Generates implementation planning artifacts from a speckit feature spec.
npx skills add https://github.com/avansover/mathcraft --skill speckit-plan-avansover
Please help me install this Agent Skill. Skill: speckit-plan Source: https://github.com/avansover/mathcraft/tree/main/.claude/skills/speckit-plan Command: npx skills add https://github.com/avansover/mathcraft --skill speckit-plan-avansover
Speckit-plan turns a feature specification into an implementation planning workflow that produces concrete design artifacts while enforcing clarification and gate rules.
.specify/extensions.yml before planning, without evaluating hook conditions.research.md to resolve NEEDS CLARIFICATION, then generates data-model.md, /contracts/, and quickstart.md as design outputs.hooks.after_plan extension hooks after artifacts are produced..specify/scripts/powershell/setup-plan.ps1 -Json and .specify/memory/constitution.md to assemble required context for planning.Run the speckit-plan skill with your $ARGUMENTS to generate research.md, data-model.md, contracts, and quickstart.md from your speckit project structure.
High-intent search queries and answers about installing and using this skill.
To generate implementation planning artifacts from a feature spec, you orchestrate a two-phase workflow that first consolidates research to resolve unknowns, then outputs a data model, contracts, and a quickstart guide.
The best way to resolve technical unknowns before creating a data model and contracts is to generate a consolidated research document that identifies and addresses all clarification requirements.
Constitution-based validation during spec-to-design planning works by reading a constitution file to assemble project context before planning, then re-checking it after design artifacts are produced to ensure compliance.
Yes, you can run custom extension hooks defined in your extensions configuration before planning starts as mandatory pre-checks, and execute post-design hooks after artifacts are produced.
Yes, you need a specific project structure that includes a setup script for JSON context parsing, a constitution file, and the required plan template workflow to generate the design artifacts.
The design artifacts produced when converting a feature specification into an implementation plan include a consolidated research document, a data model, API contracts, and a quickstart guide.
peancharoen...
nq-rdlGenerate design artifacts from an IMPL_PLAN template with extension hooks.
juanca202Convert spec-kit project tasks into GitHub issues with dependency order.
kimen-devGenerate research documents, data models, and interface contracts from project templates.