soydiloreto
UserA development pipeline your coding agent has to walk through: six phases, gates enforced outside the model, and one method wired into six tools.
Categories
Indexed Skills (17)
ddw-commit
Creates a commit following Gitmoji + Conventional Commits, with mandatory AI attribution. Trigger: /ddw-commit, when a DDW phase closes and has artifacts to commit (DEFINE, PLAN, CODE, DISCOVERY, CLOSEOUT).
ddw-context-check
Compares what the repository already declares about how it is built — linters, type checkers, CI, pre-commit, runtime versions — against what the tool's context file tells DDW. Reports the commands DDW would otherwise run wrong. Never blocks. Trigger: /ddw-context-check, and once per ticket in CLASSIFY.
ddw-create-adr
Records an architecture or design decision as an ADR (Architecture Decision Record). Captures the context, the options considered, the decision taken and its consequences. Trigger: /ddw-create-adr, during DDW's PLAN or CODE phase.
ddw-create-pr
Opens a Pull Request with a standard format and AI attribution labels, or records why one is not possible in this repo. Trigger: /ddw-create-pr, during DDW's CLOSEOUT phase.
ddw-create-prd
Creates a new PRD (Product Requirements Document) or updates an existing one. The PRD defines WHAT will be built: functional and non-functional requirements, acceptance criteria, scope and risks. Trigger: /ddw-create-prd, during DDW's DEFINE phase.
ddw-create-spec
Creates a new spec or fix-plan from an approved PRD or a fix diagnosis. Trigger: /ddw-create-spec, during DDW's PLAN phase.
ddw-eject
Copies the method out of the plugin and into this repository, so it can be read, edited and versioned with the project. After this, the repo's copy is the one that runs. Trigger: /ddw-eject, available in any DDW phase.
ddw-help
Getting-started guide for DDW. Use it when the user asks "how do I use DDW", "how do I start / install DDW", "what is DDW", or "what commands does DDW have". Trigger: /ddw-help.
ddw-security-sast
Static Application Security Testing (SAST). Scans the code for security vulnerabilities. A BLOCKING GATE — the `sast` receipt is what lets a ticket leave CODE, in every tier. Trigger: /ddw-security-sast, during DDW's CODE phase.
ddw-self-check
Full coherence validation of the internal state. Checks that the DDW installation in the repo is sound and that the pipeline state is consistent with the artifacts on disk. Read-only. Trigger: /ddw-self-check, available in any DDW phase.
ddw-status
Reads .ddw-state.json and prints a formatted summary of where the pipeline is. Read-only — it modifies no file. Trigger: /ddw-status, available in any DDW phase.
ddw-test
Runs the project's tests, generating missing ones when needed. A blocking gate. Trigger: /ddw-test, during DDW's CODE phase.
ddw-threat-modeling
Threat analysis of the proposed design. Identifies new attack surfaces and security risks before any code is written. The findings become mitigations folded into the spec. Trigger: /ddw-threat-modeling, during DDW's PLAN phase.
ddw-validate-arch
Validates that the code follows the project's architecture decisions and conventions. An advisory check, not a gate: the graph carries no `arch` condition, so it reports and the orchestrator decides. Produces disambiguation questions when a finding needs the user's context. Trigger: /ddw-validate-arch, during DDW's CODE phase.
ddw-validate-prd
Validates a PRD against the catalog's PRD rules and the project's architecture. Produces a disambiguation question for every FAIL, so gaps get resolved before approval. Trigger: /ddw-validate-prd, during DDW's DEFINE phase.
ddw-validate-spec
Validates that a spec/fix-plan is complete, coherent and consistent with its PRD, against the catalog's spec rules. Produces a disambiguation question for every FAIL. Trigger: /ddw-validate-spec, during DDW's PLAN phase.
ddw-verify-module
Verifies that a completed module meets every acceptance criterion in its PRD and every task in its spec. A blocking gate. Trigger: /ddw-verify-module, during DDW's VERIFY phase.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.