How this command is triggered — by the user, by Claude, or both
Slash command
/spec-driven-workflow:spec-init <feature-name>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Initialize Feature Specification You are initializing a new spec-driven development workflow for the feature: **$ARGUMENTS** ## Your Task 1. Create the feature slug from the name (kebab-case, lowercase) - Example: "User Authentication" -> "user-authentication" - Example: "Payment Flow" -> "payment-flow" 2. Create the directory `.specs/<feature-slug>/` 3. Create an initial `requirements.md` with this exact template: 4. Confirm the initialization was successful 5. Instruct the user to run `/spec-requirements <feature-slug>` to continue ## Important - Feature slug must be ke...
You are initializing a new spec-driven development workflow for the feature: $ARGUMENTS
Create the feature slug from the name (kebab-case, lowercase)
Create the directory .specs/<feature-slug>/
Create an initial requirements.md with this exact template:
# Requirements Document
## Introduction
[Brief description of the feature will be added during requirements phase]
## Requirements
[Requirements will be generated in the next phase]
Confirm the initialization was successful
Instruct the user to run /spec-requirements <feature-slug> to continue
npx claudepluginhub iButters/ClaudeCodePlugins --plugin spec-driven-workflow/specGenerates a feature spec via interactive Q&A on problem, users, scope, edges; fills template; runs Gate 1 checklist; saves to .planning/specs/<feature>.md
/archStarts collaborative feature specification process: investigates codebase for patterns and constraints, proposes design with reasoning and file paths, resolves ambiguities via conversation, saves Markdown spec with behavior, architecture, constraints, and related files.