Synthesizes conversation context into a structured spec document committed to the repository.
npx skills add https://github.com/MoofonLi/dev-ready --skill to-spec-moofonli
Please help me install this Agent Skill. Skill: to-spec Source: https://github.com/MoofonLi/dev-ready/tree/main/.agents/skills/to-spec Command: npx skills add https://github.com/MoofonLi/dev-ready --skill to-spec-moofonli
docs/specs/<version>/fr-NN-<slug>.md, aligned with FR numbering, the project glossary, and ADRs. - Use Case: After discussing a new feature with your coding agent, invoke this Skill to capture the agreed design as a committed spec file that gates the next step (ticket breakdown) via its Draft-to-Accepted status. ## Quick Start Ask your agent to run the to-spec skill to turn the current conversation into a spec document under docs/specs.High-intent search queries and answers about installing and using this skill.
Invoke the to-spec skill after discussing the feature with your agent. It synthesizes the existing conversation and codebase context into a structured spec with problem statement, user stories, and implementation decisions, without asking new interview questions.
The spec template includes Problem Statement, Solution, an extensive numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. Code snippets are excluded except for decision-rich prototype fragments.
Specs are written to docs/specs/<version>/fr-NN-<slug>.md, aligned with the FR numbering in requirements.md and version-plan.md. They are durable, committed documents and serve as the only lasting record of the design phase.
Avoid it when the problem space is still unclear and needs discovery first. In that case run upstream steps like grilling or domain modeling before specification, since this skill only synthesizes what has already been discussed.
The spec carries a Status line that moves from Draft to Accepted. The project owner must accept it explicitly; the workflow does not proceed to ticket breakdown until that acceptance gate is passed.
BING0116-gifInterviews users with focused questions to clarify requirements before planning or implementation.
dreamingechoesBreak feature specs into verifiable tasks with acceptance criteria and dependencies.
a35506322Stress-test project plans against domain documentation, codebase, and ADRs.
tylerburleighExtract the next actionable task from a specification and generate an execution plan.