Convert .speclet/draft.md into an executable spec.json with trackable stories.
npx skills add https://github.com/danielcastro-dev/speclet --skill speclet-spec
Please help me install this Agent Skill. Skill: speclet-spec Source: https://github.com/danielcastro-dev/speclet/tree/main/.opencode/skill/speclet-spec Command: npx skills add https://github.com/danielcastro-dev/speclet --skill speclet-spec
Converts a draft document into an executable spec.json with trackable stories, enabling structured feature delivery from informal notes.
.speclet/draft.md into .speclet/spec.json with a clearly defined feature, summary, and acceptance criteria.passes boolean for each story and supports a quick spec-lite flow for rapid fixes.Convert your draft at .speclet/draft.md into a fully formed .speclet/spec.json.
High-intent search queries and answers about installing and using this skill.
To convert a draft document into a specification, place your notes in the `.speclet/draft.md` file. The tool processes this informal draft and automatically generates a structured `spec.json` file containing functional requirements, atomic stories, and verifiable acceptance criteria.
Tracking feature development from informal notes is done by generating a `spec.json` file with atomic stories. Each story receives a boolean `passes` flag and verifiable acceptance criteria, allowing you to monitor implementation status directly from the structured specification output.
A specification generator numbers functional requirements sequentially as FR-1, FR-2, and so on. This numbering enforces structure across the generated `spec.json` file, linking each atomic story to clearly defined functional requirements and verifiable acceptance criteria for accurate tracking.
You need a specific file structure to generate trackable stories. Your draft must be located at `.speclet/draft.md` before processing. The tool reads this exact path and outputs the structured `spec.json` file directly into the `.speclet` directory.
The spec.json creation enforces required fields including feature, branch, date, summary, nonGoals, functionalRequirements, and a stories array. These fields ensure the resulting specification provides a fully structured and trackable foundation for feature delivery.
You can use a spec-lite flow for rapid fixes alongside full feature development. This flow supports converting a draft document into a `spec.json` quickly, maintaining the required fields and verifiable acceptance criteria while enabling faster tracking for smaller updates.
danielcastro-devConsolidate accepted council decisions into a spec-ready draft.md.
guifryDecompose feature requests into atomic stories with dependencies, acceptance criteria, and tests.
nguyennd93Automates story completion reviews by validating acceptance criteria and updating project management tools.
pretodevGenerate structured feature specification documents from feature definitions.