Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/spec-workflow
This skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks", "write a PRD", "technical specification", or mentions "spec-driven development", "feature spec", "requirements phase", "design phase", or "tasks phase". Provides structured 3-phase workflow for feature development.
Passed 19 of 21 test cases with the skill, and 4 of 21 without it.
and 14 more in the full report
17 fixed3 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our implementation task tracking markdown, what valid state values can be assigned to the Wired field?
| Checked | Without skill | With skill |
|---|---|---|
| Restricts task Wired field values to no, yes, or n/a. | Missed | Passed |
The instructions your model reads when the skill loads.
A structured approach to feature development through four phases: Brainstorm, Requirements, Design, and Tasks. This methodology prevents ad-hoc coding by ensuring proper planning before implementation.
Spec-driven development transforms vague feature ideas into formal, traceable specifications:
Feature Idea → Brainstorm (Conversation) → Requirements (EARS) → Design (Architecture) → Tasks (Trackable)
Before formalizing requirements, use /spec-brainstorm to explore the idea through conversation.
/spec-brainstorm [idea]/spec <feature-name>The brainstorm phase is optional — if you already know exactly what you want, skip straight to /spec.
All new spec files are stored in .claude/specs/<feature-name>/. Existing .codex/specs/<feature-name>/ specs remain supported as a migration fallback:
requirements.md - User stories with EARS acceptance criteriadesign.md - Architecture, components, data flowtasks.md - Implementation tasks tracked by status, wiring, verification, and dependenciestest cases passed, vs 4 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.