Synthesizes conversation context into a structured spec published to the project issue tracker.
npx skills add https://github.com/jwh3times/holland-vip --skill to-spec-jwh3times
Please help me install this Agent Skill. Skill: to-spec Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/to-spec Command: npx skills add https://github.com/jwh3times/holland-vip --skill to-spec-jwh3times
ready-for-agent triage label. - Use Case: After discussing a new feature with the AI, invoke this Skill to get a ready-to-implement spec filed as a triaged issue, respecting the project's domain glossary and ADRs. ## Quick Start Ask the AI to turn the current conversation into a spec and publish it to the issue tracker.High-intent search queries and answers about installing and using this skill.
Invoke the to-spec skill after discussing the feature. It synthesizes the existing conversation and codebase understanding into a structured spec with problem statement, user stories, and implementation decisions, then publishes it to the 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 covers all aspects of the feature based on the prior conversation, without requiring additional interviews.
No, implementation decisions avoid specific file paths and code snippets since they become outdated quickly. An exception exists for prototype snippets that encode decisions more precisely than prose, such as state machines or type shapes.
Testing seams are the points where a feature will be tested. The skill prefers existing seams over new ones and proposes new seams at the highest possible level, aiming for as few seams as possible across the codebase.
Avoid it when the conversation lacks enough context about the feature, since the skill does not interview the user. It also requires the issue tracker and triage label vocabulary to be configured beforehand via the setup command.
tokisakiyuuGenerates a PRD from conversation context and publishes it to the project issue tracker.
mmartinsolivBreak plans, specs, or PRDs into dependency-ordered tracer-bullet issues.
tokisakiyuuIdentifies shallow modules and proposes deepening refactors to improve codebase testability and navigability.
Prathmesh2000Enforce a brainstorm-first workflow before drafting BRDs, feature specs, and use-case documents.