Generate design artifacts and resolve technical unknowns from spec-kit projects.
npx skills add https://github.com/dmae97/oh-my-kimi --skill speckit-plan-dmae97
Please help me install this Agent Skill. Skill: speckit-plan Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/speckit-plan Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill speckit-plan-dmae97
This Skill turns an existing spec-kit project into a structured implementation planning workflow, producing design artifacts while resolving unknowns and enforcing gate checks.
hooks.before_plan and hooks.after_plan from .specify/extensions.yml when present.NEEDS CLARIFICATION items, runs research to resolve them, then generates technical design outputs.research.md, data-model.md, optional contracts/, quickstart.md, and updates the agent context file (KIMI.md) between <!-- SPECKIT START --> and <!-- SPECKIT END -->.Ask your AI to execute the speckit-plan workflow for your current spec-kit repository to generate the plan artifacts and update your agent context.
High-intent search queries and answers about installing and using this skill.
To generate implementation plans from specifications, resolve technical unknowns and produce design artifacts like data models and interface contracts. This workflow extracts JSON setups, loads templates, and enforces constitution gate checks.
Specification planning produces research.md, data-model.md, optional contracts, quickstart.md, and updates the agent context file. These artifacts provide structured technical design outputs and implementation guidance for feature development.
Evidence-gated planning handles unclear requirements by extracting NEEDS CLARIFICATION items, running targeted research to resolve them, and then generating technical design outputs. This ensures unknowns are addressed before implementation guidance is produced.
Yes, the planning workflow supports custom pre-hooks and after-hooks. It automatically runs hooks.before_plan and hooks.after_plan defined in the .specify/extensions.yml file, enabling you to inject custom logic into the process.
Yes, DAG planning for design artifacts requires an existing spec-kit project. The workflow translates feature specifications into data models and interface contracts by reading your repository and updating the agent context file.
SorinSAutomate Spec-Driven Development planning phases and generate design artifacts.
cicero78MGenerate data-model.md, contracts/, and quickstart.md from plan templates.
B0yZ4kr14Convert feature specifications and constitution into research and design artifacts.
kimen-devGenerate research documents, data models, and interface contracts from project templates.