sdd-engineering

Plugin sdd-engineering from marketplace dev-digest-ai-marketplace in humen-dev/dev-digest-ai-marketplace. Commands read from the repo's manifest — 26 days ago.

Skills (3)

• ears-requirements

  Write and review testable requirements with EARS (Easy Approach to Requirements Syntax). Use whenever acceptance criteria, edge-case rules, NFRs or untrusted-input rules are written or reviewed for a spec (the project's specs folder, written by sdd-engineering:spec-creator), when a requirement sound

• run-plan

  Executes an APPROVED implementation plan (written by sdd-engineering:implementation-planner into the project's plans directory) end to end: Wave 0 in the main session, sdd-engineering:implementer waves, sdd-engineering:plan-verifier after every wave, a review loop (architecture-review:architecture-r

• workflow-retro

  Retrospective for a finished multi-agent run — the sdd-engineering:spec-creator interview, sdd-engineering:implementation-planner, /sdd-engineering:run-plan waves, a review loop, a Workflow() fan-out or any batch of subagents. Measures what the run cost and how it flowed (tokens per agent incl. nest

Subagents (4)

• implementation-planner

  Implementation-planning agent for Spec-Driven Development. Use when a feature, refactor or multi-file change already has requirements (a SPEC-NN spec written by `sdd-engineering:spec-creator`, a design brief, or a concrete request) and needs an Implementation Plan before any code is written. It does

• implementer

  Implementation agent for Spec-Driven Development. Use to implement ONE work unit of an approved plan (`<plansDir>/<slug>.md`, written by `sdd-engineering:implementation-planner`) — any Kind except `orchestrator` (backend, ui, engine, e2e, cli … — the plan decides). Normally dispatched by `/sdd-engin

• plan-verifier

  Plan-compliance gate for Spec-Driven Development. Use after EVERY wave commit of `/sdd-engineering:run-plan` (mandatory), once no implementer is still running, and once with `scope: all` at the end, to check the finished code against an approved plan (`<plansDir>/<slug>.md`) item by item — contracts

• spec-creator

  Specification agent for Spec-Driven Development — the step before `sdd-engineering:implementation-planner`. Use when a feature needs a behaviour spec (what the system must do, not how) before planning, or when an existing spec must be revised, approved, marked implemented or superseded. The caller p

Hooks (4)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/write-guard.mjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/bash-guard.mjs"

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/trace.mjs"

• SubagentStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/trace.mjs"

Similar plugins