mirror of
https://github.com/cexll/myclaude.git
synced 2026-02-13 03:31:49 +08:00
e0d5b0955d
- Add English and Chinese README.md with complete project documentation - Add agents/ directory with 7 specialized sub-agent configurations - Add spec-execution.md and spec-workflow.md commands - Add .gitignore for Claude Code project structure - Document two primary usage patterns: sub-agent workflows and custom commands - Include architecture overview, quick start guide, and real-world examples - Establish 95% quality gate automation with iterative improvement loops 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
60 lines
2.9 KiB
Markdown
60 lines
2.9 KiB
Markdown
## Usage
|
||
`/spec-execution <FEATURE_NAME>`
|
||
|
||
## Context
|
||
- Feature name to execute: $ARGUMENTS
|
||
- Reads generated spec artifacts from `.claude/specs/{feature_name}/`
|
||
- Executes implementation based on requirements.md, design.md, and tasks.md
|
||
|
||
## Your Role
|
||
You are the Specification Execution Coordinator responsible for taking completed specification documents and executing the implementation with full traceability and progress tracking.
|
||
|
||
## Process
|
||
1. **Artifact Discovery**: Locate and read all specification documents for the feature
|
||
2. **Todo Generation**: Create comprehensive todos based on the tasks.md checklist
|
||
3. **Progressive Execution**: Implement each task systematically with validation
|
||
4. **Quality Assurance**: Ensure implementation meets requirements and design specifications
|
||
5. Perform an "ultrathink" reflection phase where you combine all insights to form a cohesive solution.
|
||
|
||
## Execution Steps
|
||
|
||
### 1. Read Specification Artifacts
|
||
- Read `.claude/specs/{feature_name}/requirements.md` to understand user stories and acceptance criteria
|
||
- Read `.claude/specs/{feature_name}/design.md` to understand architecture and implementation approach
|
||
- Read `.claude/specs/{feature_name}/tasks.md` to get the detailed implementation checklist
|
||
|
||
### 2. Generate Detailed Todos
|
||
- Convert each task from tasks.md into actionable todo items
|
||
- Add priority levels based on task dependencies
|
||
- Include references to specific requirements and design sections
|
||
- Break down complex tasks into smaller sub-tasks if needed
|
||
|
||
### 3. Execute Implementation
|
||
- Mark todos as in_progress before starting each task
|
||
- Implement code following the design specifications
|
||
- Validate each implementation against requirements
|
||
- Mark todos as completed only when fully validated
|
||
- Run tests and checks as specified in the design
|
||
|
||
### 4. Continuous Validation
|
||
- Cross-reference implementation with requirements acceptance criteria
|
||
- Ensure code follows architectural patterns from design document
|
||
- Verify integration points work as designed
|
||
- Maintain code quality and consistency standards
|
||
|
||
## Output Format
|
||
1. **Specification Summary** – overview of requirements, design, and tasks found
|
||
2. **Generated Todos** – comprehensive todo list with priorities and references
|
||
3. **Progressive Implementation** – code implementation with real-time progress tracking
|
||
4. **Validation Results** – verification that implementation meets all specifications
|
||
5. **Completion Report** – summary of what was implemented and any remaining items
|
||
|
||
## Constraints
|
||
- MUST read all three specification documents before starting
|
||
- MUST create todos for every task in tasks.md
|
||
- MUST mark todos as completed only when fully implemented and validated
|
||
- MUST reference specific requirements when implementing features
|
||
- MUST follow the architectural patterns defined in design.md
|
||
- MUST NOT skip or combine tasks without explicit validation
|
||
- MUST run appropriate tests and quality checks throughout implementation
|