sdd-engineering

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

Skills (3)

• engineering-insights

  Captures a non-obvious engineering insight (a working pattern, an antipattern/dead end, a decision with its reason, or a recurring error and fix) found while working in this repo, and files it into the INSIGHTS.md of the package the session touched. Use at the end of a session that learned something

• run-plan

  Runs the Spec Driven Development execution workflow for an already-written Implementation Plan (docs/plans/<slug>.md) — implementer tasks wave by wave along the plan's DAG, one plan-verifier pass with a fix loop, an architecture-review loop (review → fix → re-review until clean or the round cap), th

• workflow-retro

  Retrospective of a finished multi-agent workflow run (e.g. /sdd-engineering:run-plan, a code review, spec → plan → execution) — collects run facts (agents spawned, spawn order and waves, tokens per agent and per type, fix rounds, caps hit, human interventions), extracts insights per agent type (what

Subagents (4)

• implementation-planner

  Use when a feature already has an approved spec (specs/<slug>/spec.md, from spec-creator) or a clear set of requirements and needs an Implementation Plan before any code is written. Reviews the requirements, asks the user about anything unclear, gives recommendations for doing it better, asks whethe

• implementer

  Use to execute one task from an already-written Implementation Plan (docs/plans/<feature-slug>.md), or one fix task built from review/verification findings — writes and edits code for that task's owned paths only, on the current branch, applying the engineering-paved-path skills that skill-routing a

• plan-verifier

  Use after one or more tasks of a docs/plans/<slug>.md plan are reported done, to verify point by point that every Acceptance criterion and Done-condition is actually met by the code on the current branch — with evidence (file:line, test name, re-run command output). Read-only; reports MET / PARTIAL

• spec-creator

  Use when a feature/module needs a written specification for Spec Driven Development before any plan or code exists. Analyses the request and user-supplied design sources against the codebase, asks the user about gaps, ambiguities, uncovered edge cases, cross-module interaction and UX improvements, t

Hooks (1)

• PreToolUse

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

Similar plugins