crd

The crd skill is a specialized orchestration tool designed for brownfield software development, streamlining the process of requesting and implementing changes in existing codebases. It serves as the primary bridge between a developer's intent and a structured, actionable task plan. By automating the documentation and impact assessment phases, it allows engineering teams to maintain clean architectural boundaries and consistent project metadata.

At its core, this skill manages the relationship between your git history and documentation. It interacts with the PROJECT.md file to track codebase state via hashes, ensuring that context remains synchronized with the latest commits. When a user requests a change—such as adding a feature, modifying an existing module, or refactoring code—the skill automatically triggers impact analysis to identify affected components, providing developers with a clear scope before they begin implementation. This proactive approach helps prevent technical debt and reduces the cognitive load during complex code modifications.

• Automated context management using PROJECT.md to maintain up-to-date documentation for brownfield projects.

• Seamless git integration to verify repository states and handle context updates via diffs.

• Keyword-based change classification (feature-add, feature-modify, feature-remove, refactor) to standardize development tasks.

• Integrated impact analysis to evaluate how proposed changes ripple through existing code structures.

• Interactive requirements gathering, including acceptance criteria generation (Given/When/Then).

• Automated generation of structured CRD markdown files stored in the docs/crd directory.

• Built-in support for listing and status tracking of current CRDs within the development workflow.

• Requires a valid git repository as the target project path.

• Ideal for software engineers and project leads managing existing projects needing structured change management.

• Operates as a stateless skill where state is persisted directly within the project repository (PROJECT.md and CRD files).

• Serves as a foundational dependency for the larger /breakdown and /execute workflows.

• Best used in conjunction with /crd-investigate and /crd-impact-analysis for full ecosystem coverage.

• Helps maintain clear audit trails and requirements traceability for enterprise-grade feature requests.