A Claude Code plugin for managing requirement documents, tracking changes, and outputting specs. Enables downstream tools to generate code based on high-quality specs and complete E2E testing. Benefits operations teams by ensuring consistency and traceability in software development.
git clone https://github.com/mkhrdev/cc-spec-driven.gitcc-spec-driven is a Claude Code plugin that manages requirement documents, tracks changes through change records (CRs), and generates specifications for downstream code generation and testing. It implements a spec-driven, document-first workflow where confirmed documents serve as the single source of truth for development and E2E testing. The plugin automates dependency tracking, maintains consistency across feature documents, and prevents common documentation errors through engineering-level hooks. Teams use it to incrementally enrich requirements, track requirement changes with CR-ID references, and enable AI-assisted code generation and test case creation based on high-quality specs.
Install via `claude plugins:install mkhrdev/cc-spec-driven` and run `/dd-init` to initialize your product. Use `/dd-update` to create changes in natural language, `/dd-confirm` to generate RC previews, and `/dd-done` to merge to official docs. Type `/dd-` in Claude Code to see all available commands.
Initialize and manage product requirements with automatic change tracking and CR numbering
Generate development and test specifications from confirmed requirement documents
Track feature dependencies and detect missed dependency changes during confirmation
Create reusable E2E test cases with version control and CR-ID naming
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/mkhrdev/cc-spec-drivenCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
I need to manage requirement documents for [PROJECT_NAME] in [INDUSTRY]. Please help me track changes and output specs. Here are the key requirements: [REQUIREMENTS]. Ensure the output is compatible with downstream tools for code generation and E2E testing.
# Requirement Document for [PROJECT_NAME] ## Overview The following requirements have been documented and tracked for [PROJECT_NAME] in the [INDUSTRY] sector. Changes have been logged and are ready for downstream tools. ## Key Requirements - **User Authentication**: Multi-factor authentication for all user logins. - **Data Encryption**: End-to-end encryption for all sensitive data. - **API Integration**: RESTful API for third-party integrations. - **Compliance**: Adherence to [INDUSTRY] regulations and standards. ## Change Log - **2023-10-01**: Added multi-factor authentication requirement. - **2023-10-05**: Updated data encryption standards. - **2023-10-10**: Integrated RESTful API specifications. ## Output Specs The above requirements are ready for downstream tools to generate code and perform E2E testing.
Create and collaborate on interactive animations with powerful, user-friendly tools.
AI assistant built for thoughtful, nuanced conversation
Design smarter sales workflows visually
Get more done every day with Microsoft Teams – powered by AI
Agentic AI Workflow platform
Connected workspace for docs, wikis, and projects
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan