How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow-automation:feature-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
This skill produces the Spec section of a plan document — the
design, requirements, and decisions for a feature. It does NOT produce
implementation phases. After the feature-spec skill, use the feature-plan
skill (/feature-plan) to add phased implementation steps, or auto-implement
(/auto-implement) to plan and ship in one flow.
Brainstorm = "what and why" (Spec section of the plan). Plan = "how and when" (Implementation Plan section).
Before asking questions, understand the landscape:
Before diving into questions, give the user a concise overview of what you found and what needs to be decided. Output a short message (not a tool call) covering:
This gives the user a mental map of the feature spec before the first question arrives. Keep it brief — aim for 8-15 lines total. Do not use AskUserQuestion for this step; just present the overview as text.
Use AskUserQuestion as the default interaction tool — one question at a time, prefer multiple choice with descriptions.
Before every question, output a brief context summary as plain text (not inside AskUserQuestion). This keeps the user oriented as the interview progresses. The summary should include:
Keep the summary to 3-5 lines — enough to provide context, not so much that it becomes a wall of text. Then immediately follow with the AskUserQuestion call.
Focus on understanding:
Key principles:
When you understand the problem well enough, propose 2-3 approaches using AskUserQuestion:
Iterate on the chosen approach:
Write the Spec section into a plan document:
plans/ subfolder. If no convention is found, use the
project root.plan-<kebab-case-name>.md../feature-plan/references/plan-template.md. Fill in the ## Spec
section and its subsections. Leave the ## Implementation Plan
section with placeholder content — the feature-plan skill fills
that in.Spec to IN_PROGRESS. Leave Plan and all
phases as TODO.Spec subsections to fill in:
Run one automatic review after writing the spec — do not ask the user whether to review.
Spawn a review agent using the Agent tool
(subagent_type="feature-dev:code-architect") with this focus prompt:
"Review this spec (the ## Spec section of the plan document)
against the existing codebase. Verify:
(1) feasibility — do the referenced APIs, patterns, and constraints
hold in the current codebase,
(2) completeness — are there missing requirements, edge cases, or
architectural concerns,
(3) consistency — do design decisions align with each other and with
project conventions,
(4) scope — is the scope clear and realistic, are in/out boundaries
well-defined.
For each finding, state severity (blocker/warning/suggestion) and a
concrete recommendation. End with: Review complete: X findings
(Y blockers, Z warnings)."
Handle feedback:
After all blocker revisions are applied, mark Spec as DONE in
the status table.
Fallback: If the Agent tool is unavailable, note in the Review Feedback section that the spec was not independently reviewed and present it directly.
Ask the user via AskUserQuestion whether to proceed:
"Spec written and reviewed (
<path>). What next?"
Options:
If the user selects "Yes, proceed to /feature-plan", immediately invoke the feature-plan skill (via the Skill tool) with the spec doc path as context, noting that design decisions are already resolved in the spec.
If the user selects "Plan and ship", immediately invoke the auto-implement skill (via the Skill tool) with the spec doc path as context.
Do NOT write code during the feature-spec skill. This skill produces a spec,
not implementation. If the user asks to start coding, suggest completing
the feature spec first, then using /feature-plan followed by /implement.
spec-*.md file instead of the plan documentnpx claudepluginhub matthiaskloft/claude-skills --plugin workflow-automationGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.