sdd-engineering

Plugin sdd-engineering in SyukPublic/ai-dev-toolkit. Commands read from the repo's manifest — 23 days ago.

Skills (4)

• engineering-insights

  Capture durable engineering insights into the host project's insights file (default docs/engineering-insights.md), and prune that log. Use during any session when a non-obvious discovery is confirmed — a gotcha, a fix's root cause, a why-it's-like-this decision, an antipattern, or a tool/library qui

• 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

  Executes an APPROVED Development Plan through the SDD implementation pipeline: implementer wave(s) → test-writer gap pass → green barrier (tests + typecheck) → architecture-reviewer ∥ plan-verifier → bounded fix loop (max 2 iterations) → final report. HARD GATE: an existing plan file is a required i

• workflow-retro

  Post-run retrospective of the multi-agent SDD pipeline (spec-creator → implementation-planner → implementer / test-writer → architecture-reviewer / plan-verifier, plus nested researcher/Explore agents). Manually invoked after a run to produce TRUE token/tool/duration/parallelism metrics — deep mode

Subagents (5)

• implementation-planner

  Spec-driven planning specialist that turns an APPROVED feature spec (default convention docs/specs/SPEC-*.md) into a structured, traceable "Development Plan" at docs/plans/<feature>.md (default convention; the caller may pass different paths for both). Use when the user asks to "plan", "design", "br

• implementer

  Implementation specialist that ships the code for a single planned slice of a project — UI or backend. Use PROACTIVELY to implement one disjoint phase of a Development Plan (default convention docs/plans/*.md; the caller may pass a different path), or any well-scoped coding task. It is safe to run s

• plan-verifier

  Verifies that implemented code matches the plan / specification: "verify against the plan", "does the code match the spec", "requirement coverage", "what's missing from the spec", "check implementation against the plan", "is the SPEC implemented", "did we implement everything". Read-only agent focus

• spec-creator

  Spec-Driven Development specialist that produces complete, unambiguous feature specifications for any project. Use when the user asks to "write a spec", "specification", "spec out a feature", "acceptance criteria", "EARS", or to analyze a design (Figma export / claude.ai design / mockup images) for

• test-writer

  Triggered by: "write tests", "add tests", "cover with tests", "unit test", "integration test", "test this component", "test this route", "test this service", "RTL", "vitest". Writes ONLY to test files; never modifies production source. Unlike implementer (which writes production code AND tests for a

Similar plugins