Help us improve
Share bugs, ideas, or general feedback.
From dev-workflow
Generates spec documents (order.md) and task checklists (todo.md) for features, bugfixes, improvements, spikes, or chores. Auto-detects scenario, analyzes codebase patterns. Use before implementation.
npx claudepluginhub kzytateishi/spikeee-plugins-marketplace --plugin dev-workflowHow this skill is triggered — by the user, by Claude, or both
Slash command
/dev-workflow:specifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a specification for `$ARGUMENTS`.
Creates task specifications via codebase analysis, interactive clarifying questions on scope/constraints/edge cases, feature splitting checks, and agent delegation setup.
Writes structured specifications before coding. Use when requirements are ambiguous, starting a new project/feature, or changes touch multiple files.
Creates specs and phased file-level implementation plans for features, bugs, refactors by researching codebase with search, graph queries, and context files.
Share bugs, ideas, or general feedback.
Generate a specification for $ARGUMENTS.
Analyze the user's request and classify into one of 5 scenarios:
New Feature — keywords: "new", "add", "create", "build", "introduce" → Use refs/template-new-feature.md
Improvement — keywords: "improve", "optimize", "enhance", "update", "refine" → Use refs/template-improvement.md
Bugfix — keywords: "bug", "error", "fix", "broken", "crash", "failing" → Use refs/template-bugfix.md
Spike (Technical Investigation) — keywords: "investigate", "PoC", "spike", "research", "evaluate"
→ Use refs/template-spike.md
— Also triggered by explicit prefix: /specify spike: ...
Chore (Technical Work) — keywords: "refactor", "migrate", "dependency", "chore", "upgrade", "infrastructure"
→ Use refs/template-chore.md
— Also triggered by explicit prefix: /specify chore: ...
Ambiguity handling: If the request matches keywords from multiple scenarios (e.g., "fix and improve"), STOP immediately. Output a message asking the user to choose between the top 2 matching scenarios. Do not proceed to Phase 2 until the user replies.
No match: If no keywords match any scenario, ask the user which scenario best fits their request.
Before writing the specification, thoroughly analyze the existing codebase:
Using the scenario-appropriate template from refs/, generate the specification:
Create a todo.md with actionable implementation tasks:
- [ ] checkbox formatCreate two files:
order.md — Specification and implementation guidetodo.md — Task checklist in - [ ] formatDerive {feature-name} as a concise kebab-case identifier from $ARGUMENTS (e.g., "user authentication flow" → user-auth-flow). Default output directory is specs/{feature-name}/. If the user specifies a different directory, use that instead.
/implement {feature-name} to start implementation