sdd-engineering

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

Skills (2)

• run

  Manual-only retrospective of a finished multi-agent workflow (for example /implement, or spec-creator → planner → implementer → reviewer → verifier). Reports tokens, agent count and launch order, friction, duplicated work and gaps, proposes improvements, and appends a ledger entry to docs/retro/ledg

• specification-driven-development

  Use when a feature needs explicit acceptance criteria, an implementation plan, and evidence that each requirement is covered. Describes the spec → plan → implement → verify loop and which sdd-engineering component handles each stage.

Slash commands (1)

• /sdd-engineering:implement

  Spec-driven implementation — runs a ready Implementation Plan via implementer agents, then architecture review + fix loop, then plan-verifier. Does NOT run spec-creator, implementation-planner or test-writer.

Subagents (6)

• doc-writer

  Documents implemented features — turns a Development Plan or validation report (or existing code) into documentation with mermaid diagrams. Knows where to write: package README, docs/specs/, root docs/. Write/Edit are limited to Markdown documentation files. Use after the implementation is confirmed

• implementation-planner

  Creates an Implementation Plan from a ready specification or requirements — validates the requirements, asks clarifying questions, recommends improvements, splits the work into steps with skills and a test strategy, and asks the user for the execution mode (multi-agent or single-agent). Does not wri

• implementer

  Executes ONE step (or a group of steps of one package) of an Implementation Plan — writes code, applies the skills named in the plan, and runs only cheap targeted checks. Does not write new tests, does not do architecture review, does not run full test suites or lint. Also fixes review/verifier find

• plan-verifier

  Checks the implemented code against every item of a Development Plan or requirements — a Coverage Matrix (Verified / Not Verified + evidence) compatible with docs/specs/NN-validation-*.md. Not an audit (that is the separate convention for a plan BEFORE code). Read-only, except for running the packag

• spec-creator

  Writes feature specifications for Spec Driven Development (EARS acceptance criteria AC-N, edge cases, NFRs, [NEEDS CLARIFICATION]) and analyzes designs and mockups for gaps, uncovered edge cases, module interaction and UX improvements. Writes only Markdown under docs/specs/** (one module) or specs/*

• test-writer

  Writes tests for UI and backend code following the testing skills and conventions the project uses. Edits only test files (*.test.*, *.spec.*) — never product code. Use when you need to close the test coverage of a Development Plan step or requirement.

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/trace-version.sh"

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/path-guard.sh"

Similar plugins