From sdd
Reads project git branch, workflows directory, and SDD settings to suggest next actions, explains intent, and requests explicit approval before executing via /sdd-run.
npx claudepluginhub liorcohen/sdd --plugin sddcommands/# /sdd Your SDD workflow assistant. Reads project context, understands natural language, and guides you through the spec-driven development lifecycle. ## How It Works `/sdd` is the hub command. It knows about: - **`/sdd-help`** — for learning SDD concepts and methodology (refer novices here) - **`/sdd-run`** — for direct, explicit commands (show power users the equivalent) ## Strict Approval Protocol **NEVER execute actions without explicit user approval.** Every interaction follows this pattern: 1. **Understand** — read context, interpret the user's request 2. **Explain** — tell the ...
/feature-planningGuides feature planning workflow: gathers description/reqs interactively, generates PRD/SDD, creates planning dir, outputs TASKS.json/MD.
/workRuns main spec development workflow: select task (specific ID, epic, or next ready respecting deps), then plan/implement/verify/done with user control, session recovery, and git ops.
/startDetects and routes to new spec creation, resume existing, or quick mode. Handles git branch, parses args/flags like --fresh --quick, scans specs dir.
/spartanDetects project context, git branch, active sessions, and user intent; routes to the best Spartan AI Toolkit workflow leader or command.
/devteam-planConducts interactive requirements gathering, researches codebase, creates PRD, and generates development plan with tasks and sprints. Supports spec files, folders, and auto-detection.
/implementImplements discussed feature from chat or args using full agent workflow without tickets: loads skills, plans, codes, tests, creates open PR (steps 0-9 nonstop).
Share bugs, ideas, or general feedback.
Your SDD workflow assistant. Reads project context, understands natural language, and guides you through the spec-driven development lifecycle.
/sdd is the hub command. It knows about:
/sdd-help — for learning SDD concepts and methodology (refer novices here)/sdd-run — for direct, explicit commands (show power users the equivalent)NEVER execute actions without explicit user approval. Every interaction follows this pattern:
/sdd-run command)sdd-runThis is non-negotiable. Natural language interpretation can misfire — the approval step catches misunderstandings before they become actions.
Example:
User: /sdd I want to add user authentication
Assistant: I understand you want to create a new feature change for user
authentication. I would run:
/sdd-run change create --type feature --name user-auth
This will start the spec-driven workflow — first gathering requirements,
then creating a spec for your review.
Shall I proceed?
User: yes
Assistant: [Invokes Skill(sdd-run, args: "change create --type feature --name user-auth")]
Read project context and suggest the most relevant next action.
git branch --show-current
sdd/workflows/ directory
sdd/sdd-settings.yaml exist?sdd-settings.yamlOn a feature branch: Focus on the workflow matching that branch. Show its current phase and suggest the next action.
Current branch: feature/user-auth
Active change: user-auth-1 (User Authentication) — spec_review
The spec is ready for your review.
SUGGESTED: Review the spec, then approve it.
I would run: /sdd-run change approve spec user-auth-1
Shall I proceed, or would you like to do something else?
On main with active workflows: List all active workflows with their current phases.
You have 2 active workflows:
1. user-auth-1 (User Authentication) — plan_review
Branch: feature/user-auth
2. payment-1 (Payment Integration) — implementing
Branch: feature/payment
Which would you like to work on, or would you like to create a new change?
No active workflows: Suggest creating a new change or show general project status.
No active workflows found.
You can:
- Start a new feature: tell me what you want to build
- Import an external spec: provide a path to a spec file
- Check project status: /sdd-run version
What would you like to do?
Not an SDD project (no sdd-settings.yaml):
This doesn't appear to be an SDD project yet.
To get started:
- Learn about SDD: /sdd-help
- Initialize this project: I can run /sdd-run init
Would you like me to initialize this project?
Interpret the natural language request and map it to a /sdd-run command.
/sdd-run namespace and action| User Says | Interpreted As |
|---|---|
| "I want to create a new feature" | /sdd-run change create --type feature |
| "I want to import an external spec" | /sdd-run change create --spec <path> |
| "I want to approve the spec" | /sdd-run change approve spec <change-id> |
| "I want to approve the plan" | /sdd-run change approve plan <change-id> |
| "I want to start planning" | /sdd-run change plan <change-id> |
| "I want to start implementing" | /sdd-run change implement <change-id> |
| "I want to verify the implementation" | /sdd-run change verify <change-id> |
| "I want to submit for review" | /sdd-run change review <change-id> |
| "I want to answer an open question" | /sdd-run change answer <change-id> ... |
| "I want to go back to the spec phase" | /sdd-run change regress <change-id> --to spec |
| "I want to initialize a new project" | /sdd-run init |
| "What version am I running?" | /sdd-run version |
| "I want to configure permissions" | /sdd-run permissions configure |
| "I want to continue" | /sdd-run change continue <change-id> |
| "I want to request changes" | /sdd-run change request-changes <change-id> |
Additional intent mappings are provided by active tech packs. Load them via:
INVOKE techpacks.loadSkill with:
namespace: <tech-pack-namespace>
skill: "capabilities"
The capabilities skill returns tech-pack-specific intent→command mappings (e.g., database setup, config generation, local environment management).
When the user's intent is ambiguous, ask for clarification before suggesting a command.
When the change-id is needed but not provided, infer it from context:
user-auth-1 belongs to workflow user-auth) — no scanning neededWhen users describe settings changes in natural language (e.g., "I want to add a new component", "enable monitoring for my service"), delegate to the project-settings skill internally. Do NOT route these through /sdd-run — settings are managed by the skill directly.
/sdd-helpIf the user seems unfamiliar with a concept:
You mentioned "specs" — if you'd like to learn more about the spec-driven
approach and how specs work in SDD, try /sdd-help.
/sdd-runAfter completing or suggesting an action, show the direct equivalent:
You can also run this directly next time:
/sdd-run change approve spec user-auth-1
Welcome! This project hasn't been set up with SDD yet.
- To learn about SDD first: /sdd-help
- To initialize right away: I can run /sdd-run init for you
When the user approves an action, invoke via the Skill tool:
Skill(sdd-run, args: "change create --type feature --name user-auth")
NEVER inline /sdd-run logic. Always delegate via the Skill tool to keep the two commands decoupled.