cdd-implement

Implement DECIDED decisions into code with compliant commit messages.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/yutaro0915/cdd-workflow --skill cdd-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdd-implement
Source: https://github.com/yutaro0915/cdd-workflow/tree/main/src/templates/skills/cdd-implement
Command: npx skills add https://github.com/yutaro0915/cdd-workflow --skill cdd-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates translating DECIDED decisions into concrete implementation steps within a disciplined cdd workflow, ensuring developers verify decisions, update statuses, and produce traceable commits.

Core Features & Use Cases

  • Verify and load the cdd.md for a given decision and confirm decisionStatus is DECIDED.
  • Guide and enforce the implementation process according to the Selection section, without modifying Rejections.
  • Manage status transitions, track changed files, and generate a standards-compliant commit message for review.

Quick Start

Follow the on-screen prompts to implement a completed decision, updating statuses and creating a proper commit.

Frequently Asked Questions about cdd-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a decided architecture decision into implemented code automatically?

To implement decided decisions, the Skill verifies decisionStatus is DECIDED in cdd.md, enforces Selection constraints, updates status to IN_PROGRESS, and generates a standards-compliant commit message for review readiness.

How do I generate a compliant git commit message from a decision tracking workflow?

Generating a compliant git commit message requires tracking changed files during implementation and structuring the commit based on the decision's context. The workflow ensures the commit aligns with the Selection and Rejections constraints for traceability.

What is a decision-driven development workflow for code implementation?

A decision-driven development workflow ensures that code implementation strictly adheres to previously approved technical selections. It manages status transitions from DECIDED to IN_PROGRESS and ultimately IN_REVIEW, maintaining strict traceability between decisions and code changes.

Can I modify rejected technical approaches while implementing an approved decision?

No, the implementation process enforces adherence to the Selection section while strictly preserving the Rejections constraints. The workflow ensures developers do not modify or override the rejected alternatives during the status update and coding process.

Does this workflow require a specific status before starting code implementation?

Yes, the workflow requires the decisionStatus to be explicitly set to DECIDED before implementation begins. It verifies this status in the cdd.md file and then automatically updates it to IN_PROGRESS to track the active coding phase.