sdd-engineering

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

Skills (4)

• engineering-insights

  Appends non-obvious engineering findings to INSIGHTS.md in the package root nearest to the touched files (the directory with the package manifest), else in the repository root. Use when a non-trivial bug is diagnosed, a surprising codebase, tool or library behaviour is found, a design decision is ma

• mermaid-diagram

  Create Mermaid diagrams in markdown. Use when the user wants to visualize workflows, architectures, API flows, data models, state machines, or system designs. Covers flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, and more.

• run-plan

  Runs an already-approved Implementation Plan (written by sdd-engineering:implementation-planner) end-to-end: budget check → implementer agents per the plan's DAG (multi-agent capped by max-parallel, or single-agent) → review gate (architecture-review:architecture-reviewer + one correctness reviewer

• workflow-retro

  MANUAL ONLY — type /sdd-engineering:workflow-retro; the model never starts it on its own. Retrospective for a finished multi-agent run (/sdd-engineering:run-plan, the spec-creator → implementation-planner → implementer chain, a Workflow() fan-out, any batch of sub-agents). Collects tokens, cache rea

Subagents (5)

• implementation-planner

  Use proactively when an APPROVED feature spec (from spec-creator) needs an Implementation Plan before any code is written — the HOW and IN WHAT ORDER of Spec-Driven Development. Read-only architect that first verifies the spec (atomic EARS ACs, no contradictions, explicit non-goals, no open [NEEDS C

• implementer

  Use proactively to implement ONE task/slice from an Implementation Plan (written by implementation-planner). Handles backend (Fastify/Drizzle/onion) and UI (Next.js/React) work, applies the correct skill set per task type, follows the project's own conventions, and self-verifies with the package's e

• plan-verifier

  Read-only requirements-completion checker and the FINAL step of the SDD pipeline. Use after a feature is claimed done to verify, for every acceptance criterion (AC-N) of the spec, that a plan task, a real implementation, a test and a commit exist — a traceability matrix AC → task → test → commit, pl

• spec-creator

  Use proactively when a feature or behaviour change needs a written specification before any plan or code exists — the WHAT and WHY of Spec-Driven Development. Walks the request through six clarification categories, checks the real system state in the code and the project's docs, analyses designs (te

• test-writer

  Use proactively to add or extend unit/integration tests — backend services and routes (Fastify/Drizzle), pure domain or library code, and UI components when the plan assigns them. In the SDD pipeline it derives tests from the spec's acceptance criteria (AC-N) BEFORE reading the implementation, so te

Hooks (1)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/restrict-writes.sh

Similar plugins