Generate a structured spec from conversation context and publish it to the project issue tracker.
npx skills add https://github.com/Yassimba/loom --skill to-spec-yassimba
Please help me install this Agent Skill. Skill: to-spec Source: https://github.com/Yassimba/loom/tree/main/skills/to-spec Command: npx skills add https://github.com/Yassimba/loom --skill to-spec-yassimba
High-intent search queries and answers about installing and using this skill.
Invoke the to-spec skill after your design conversation. It synthesizes the existing context into a spec covering problem statement, solution, user stories, implementation decisions, and testing decisions, then publishes it to your issue tracker.
The skill generates an extensive numbered list of user stories in the format 'As an <actor>, I want a <feature>, so that <benefit>'. It derives them from the conversation context rather than asking you to enumerate them manually.
The skill falls back to Beads when the br command is installed, otherwise it writes the spec to local Markdown files. Running /loom initializes the project and configures the tracker.
No, the spec template explicitly excludes file paths and code snippets because they become outdated quickly. The exception is prototype snippets that encode a decision more precisely than prose, such as state machines or type shapes.
Test seams are the boundaries at which a feature will be tested. The skill prefers existing seams at the highest possible level, proposes new ones only when needed, and confirms the choice with the user before writing the spec.
tomrfordInterrogate plan decision points to resolve uncertainties and produce a design outline.
MaxWolf-01Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.
valorisaIdentify shallow modules and architectural friction points in codebases.
busboom-software-studioApply small targeted changes directly on master with test suite runs.
