sdd-skills

Plugin sdd-skills from marketplace SDD-Skill in CodeMachine0121/SDD-Skill. Commands read from the repo's manifest — 26 days ago.

Skills (9)

• architecture

  Phase between PRD and implement. Reads a feature's PRD.md and designs the technical approach — the change scope and the new classes/modules with their responsibilities — from the perspective of the next engineer who has to extend it, so future requirements land with minimal load. Outputs ARCH.md. Ne

• clarify

  Reach 100% intent consensus with the user, pin the intent down with concrete examples that cover boundaries and exceptions, then compile a requirements brief written purely in business language for handoff to PRD. Never edits source code. Triggered by: "clarify", "/clarify".

• commit

  The commit convention for this workflow — English Conventional Commits, one commit per completed TDD cycle or app integration, and no SDD identifiers (test-case ids, AC numbers, document names) in the message. Use it standalone to stage and commit the current work, or as the convention that /impleme

• contract

  Verify an implementation conforms to its contract — the feature's PRD.md (preferred; its Gherkin acceptance-criteria scenarios) or BRIEF.md — using the Acceptance Criteria as the oracle. For each clause, first derive the expected outcome from the spec alone, then judge independently whether the test

• implement

  Implement a feature against its PRD.md (acceptance criteria) and ARCH.md (technical design), letting the developer pick the discipline: TDD (red-green-refactor, one case at a time) or CODE-FIRST (build the slice whole, then cover it with tests to 100% of the changed code). Both modes pin the accepta

• improve-codebase

  Improve the design quality of an existing codebase by identifying fragmented logic and consolidating it into deep modules — simple interfaces hiding complex internals. Triggered by: "improve codebase", "deep module", "/improve-codebase".

• prd

  Two modes: (1) FEATURE — conduct a requirements interview and generate a business-language PRD under .sdd/, turning the brief's requirement examples into Gherkin acceptance criteria; (2) PROJECT — analyze UL-MAP.md and project architecture to produce or update .sdd/PROJECT.md (vision, tech stack, co

• ubiquitous-language-mapping

  Manage a Ubiquitous Language Map — bridges business terms, code names, and UI labels within a Bounded Context. Use when: initializing a new UL map, or updating/reconciling an existing one. Triggered by: "ubiquitous language", "UL map", "domain glossary", "/ul-init", "/ul-update".

• visionize

  Turn a feature's BRIEF.md and/or PRD.md into a single self-contained HTML page that visualizes the plan — goal, scope, personas, user stories, business flow, acceptance criteria (as Gherkin scenarios), and risks — using diagrams and charts so developers can see what is being built at a glance. Never

Hooks (1)

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/jev_check_doc.py"

Similar plugins