sdd
Spec-Driven Development workflow with clarification gate, blast-radius mapping, drift detection, steering docs, postmortem learning, stack detection, security review, estimates and a tasks commit guard. Stack-agnostic.
Plugin sdd from marketplace keel in IrvinngB/keel. Commands read from the repo's manifest — 1 month ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
What it installs
Skills (1)
sdd-workflowSpec-Driven Development pipeline contract for this project. Read before running or coordinating any SDD command or phase subagent — defines the artifact layout, phase graph, workload guards, and steering docs.
Slash commands (15)
/sdd:applyImplement tasks — write code following specs and design
/sdd:archiveArchive a verified change — sync delta specs into source of truth, close the cycle
/sdd:blastMap every consumer of the code about to change — what breaks if we touch X?
/sdd:clarifyForce the uncomfortable questions on a spec before design
/sdd:continueRun the next dependency-ready SDD phase
/sdd:driftDetect divergence between approved specs/design and the actual code
/sdd:estimateEstimate complexity, time and risk per task from the tasks artifact
/sdd:exploreExplore and investigate an idea — reads the codebase, compares approaches
/sdd:ffFast-forward planning — proposal, spec, clarify, design, blast-radius, tasks in sequence
/sdd:initInitialize SDD in this project — detect stack, bootstrap config and steering docs
/sdd:newStart a new SDD change — exploration then proposal
/sdd:postmortemLearn from a completed change — plan vs reality, proposed updates to steering
/sdd:securityLanguage-agnostic security review of a change's diff or a file range
/sdd:steerRefresh project steering docs (product, tech, structure)
/sdd:verifyValidate implementation against specs, design, and tasks with real test runs
Subagents (16)
sdd-applyUse when tasks are ready and code must be written following specs and design. Implement code changes from the task checklist. Reads tasks/spec/design, implements, tests, and marks tasks complete.
sdd-archiveUse after verification passes. Archive a completed and verified change: merge delta specs into main specs, move the change folder to the archive, persist the final report. Completes the SDD cycle.
sdd-blast-radiusUse after sdd-design and before sdd-tasks, or standalone to ask what breaks if X changes. Map every real consumer of the code about to change — call sites, routes, DB tables, published APIs, tests — before apply.
sdd-clarifyUse between sdd-spec and sdd-design. Detect ambiguities, hidden assumptions, and unverified claims in a spec before the design phase. Produces pointed questions (with recommended defaults) that force the uncomfortable decisions to the surface.
sdd-designUse after the spec and the clarify gate are done and the implementation approach must be chosen before task breakdown. Create the technical design document with architecture decisions, data flow, and file changes.
sdd-driftUse before verify/archive, or anytime a change folder has been open for a while. Detect divergence between approved specs/design and the actual code — changes made outside sdd-apply, or specs that went stale. Compares git history of code files against artifact dates.
sdd-estimateUse after sdd-tasks, before committing to a sprint or quoting work to a client. Estimate complexity, time and risk per task from an existing tasks artifact. Flags high-risk work (auth, payments, destructive migrations, public API changes).
sdd-exploreUse when asked to think through a feature, investigate a codebase, map modules, compare approaches, or clarify requirements — before any proposal or spec is written. Explore and investigate ideas before committing to a change. Research only; the only artifact it may write is the change's explore key
sdd-postmortemUse after sdd-archive — this is how the pipeline improves with use. Compare an archived change's plan against the actual git history, extract lessons, and propose (never auto-apply) updates to steering docs.
sdd-proposeUse when exploration is done (or the user described the change directly) and it must be formalized into a proposal document before specs. Create a change proposal with intent, scope, and approach.
sdd-securityUse standalone or from sdd-verify when security_review is on. Language-agnostic security review (OWASP-style checklist) of a change's diff or an explicit scope of files. Complements stack experts; covers what stack reviews tend to skip.
sdd-specUse when a proposal is approved and the change needs formal behavioral requirements before design and implementation. Write delta specifications with requirements and Given/When/Then scenarios.
sdd-steerUse after apply batches and after archiving a change — prevents the project context from rotting between sessions. Keep project-level steering docs (steering/product, steering/tech, steering/structure) in sync with reality.
sdd-tasksUse when spec and design are ready and the change must be sliced into ordered, actionable work items before apply. Break a change into an implementation task checklist with a review workload forecast.
sdd-verifyUse when apply reports done (or partial) and the change must be proven compliant before archive. Validate implementation against specs, design, and tasks with real test execution.
stack-detectorUse during sdd-init, or when config.yaml is missing or stale. Inspect a repository and produce a machine-usable stack profile: languages, frameworks, test runners and commands, lint/format/build commands, layers, and which project expert-agents fit.
Hooks (1)
- PreToolUse
${CLAUDE_PLUGIN_ROOT}/hooks/tasks-guard.sh
Maintain sdd?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.