Generate implementation plans from feature specs into research, data models, and contracts.
npx skills add https://github.com/a2mus/smart-da3m --skill speckit-plan-a2mus
Please help me install this Agent Skill. Skill: speckit-plan Source: https://github.com/a2mus/smart-da3m/tree/main/.agents/skills/speckit-plan Command: npx skills add https://github.com/a2mus/smart-da3m --skill speckit-plan-a2mus
Speckit Plan turns raw feature specifications into a structured, actionable technical implementation plan so teams avoid ad-hoc design work, missed requirements, and inconsistent artifacts. It standardizes the workflow for resolving unknowns, documenting research, defining data models and contracts, and preparing agent context updates to accelerate development handoffs.
Generate an implementation plan from the feature spec at .specify/specs/my-feature.yaml and produce research.md, data-model.md, and contracts for the implementation branch.
High-intent search queries and answers about installing and using this skill.
Generating a technical implementation plan from a feature specification involves parsing the spec to populate an IMPL_PLAN template with technical context and gates. This process produces research, data models, and contracts to standardize the development workflow and avoid ad-hoc design.
The spec-kit structure is a project directory format utilizing a .specify/ directory to hold feature specs and repository scripts. It standardizes software planning by producing research, data-model, and contract artifacts during Phase 0 and Phase 1 planning to accelerate development handoffs.
Creating data models and API contracts from feature specs requires parsing the specifications to resolve unknowns and define entities. The workflow produces a data-model.md for entities and validations, alongside a contracts/ directory for interfaces to prepare for implementation.
Spec-kit plan integrates with existing project setups by reading the project constitution and agent context to evaluate gates. It updates agent-specific context files and flags unresolved items as NEEDS CLARIFICATION, ensuring the implementation plan aligns with your established project rules.
Unresolved requirements are handled during implementation plan generation by flagging them explicitly as NEEDS CLARIFICATION in the final output. This ensures that missing information in the feature spec is documented in the research artifacts rather than blocking the technical context setup.
B0yZ4kr14Archive merged feature specs into .specify memory with conflict detection.
peancharoen...
cicero78MGenerate data-model.md, contracts/, and quickstart.md from plan templates.
agol586Enforce a structured planning phase with research, data models, and interface contracts.
