Execute feature specifications with intelligent automation, comprehensive validation, and progress tracking.
Executes feature specifications with intelligent automation, comprehensive validation, and progress tracking.
/plugin marketplace add nicknisi/claude-plugins/plugin install spec-driven@nicknisiExecute feature specifications with intelligent automation, comprehensive validation, and progress tracking.
# Load specification
SPEC_FILE="$ARGUMENTS"
SPEC_NAME=$(basename "$SPEC_FILE" .md)
PRP_FILE="PRPs/${SPEC_NAME}.md"
# Auto-generate or update PRP if needed
if [ ! -f "$PRP_FILE" ] || [ "$SPEC_FILE" -nt "$PRP_FILE" ]; then
echo "Generating PRP from spec..."
/generate-prp "$SPEC_FILE"
fi
# Extract metadata from spec
COMPLEXITY_SCORE=$(grep "Complexity Score:" "$SPEC_FILE" | cut -d: -f2)
ESTIMATED_EFFORT=$(grep "Estimated Effort:" "$SPEC_FILE" | cut -d: -f2)
# Discover project structure and conventions
find . -maxdepth 3 -name "*.config.*" -o -name "*rc.*" -o -name "Makefile"
# Identify test patterns
find . -type f -name "*test*" -o -name "*spec*" | head -5
# Check for existing similar features
grep -r "similar_pattern" --include="*.ts" --include="*.js" --include="*.py"
Based on spec complexity score:
From Spec Section: Technical Architecture
Database Changes (if specified in spec)
API Structure (if specified in spec)
Core Data Structures
Validation Checkpoint:
From Spec Section: Implementation Checklist
Work through each item in the spec's implementation checklist:
Continuous Validation:
From Spec Section: Dependencies and Integration
Connect Components
Data Flow
Validation Checkpoint:
From Spec Section: Testing Strategy
Execute test plan from specification:
Coverage Areas:
From Spec Section: User Stories
Code Documentation
User Documentation
Track progress through spec requirements:
[✓] Database schema created
[✓] API endpoints defined
[⏳] Frontend components built
[ ] Integration complete
[ ] Tests passing
[ ] Documentation updated
## Implementation Progress
### Completed
- [List completed spec requirements]
### In Progress
- [Current work items]
### Remaining
- [Outstanding spec requirements]
### Issues & Blockers
- [Any problems encountered]
### Validation Results
- [Test results if available]
- [Manual testing outcomes]
continue - Proceed to next phasestatus - Show current progressvalidate - Run validation checkspause - Stop for manual workskip - Skip current item (with warning)retry - Retry failed operationcheck-spec - Verify against specificationtest - Run relevant testslint - Check code qualityreport - Generate progress reportchecklist - Show implementation checklistmetrics - Display execution metricsContinue automatically when:
Pause for confirmation when:
Required for:
The command adapts to project conventions:
# Execute a specification
/execute-spec specs/user-auth-spec.md
# Execute with auto-progression
/execute-spec specs/feature-spec.md --auto
# Execute specific phase
/execute-spec specs/api-spec.md --phase=3
# Dry run to preview changes
/execute-spec specs/new-feature.md --dry-run
The execution is driven entirely by the specification document, ensuring that implementation matches requirements exactly while adapting to each project's unique structure and conventions.