Workflow: New Feature
Complete guide to add a new feature.
1
Explore
/work:work-explore→
2
Specify
/work:work-specify→
3
Plan
/work:work-plan→
4
TDD
/dev:dev-tdd→
5
Audit
/qa:qa-loop→
6
PR
/work:work-prQuick command
/work:work-flow-feature "Feature description"
This command automatically launches the complete workflow.
Detailed steps
1. Explore
/work:work-explore
Understand the existing code and identify:
- Where to add the feature
- The patterns to follow
- The potential impacts
2. Specify (optional)
/work:work-specify "Feature description"
Create a formal specification if the feature is complex:
- User stories
- Acceptance criteria
- Edge cases
3. Plan
/work:work-plan
Plan the implementation:
- Files to create
- Files to modify
- Required tests
- Identified risks
4. Code
/dev:dev-tdd "Implement the feature"
Develop with TDD:
- Write the tests
- Implement the code
- Refactor if necessary
5. Review
/qa:qa-review
Verify the quality:
- Clean code
- Complete tests
- Up-to-date documentation
6. PR
/work:work-pr
Create a Pull Request:
- Descriptive title
- Complete description
- Test checklist
Concrete example
# Add a notification system
> /work:work-flow-feature "Add a push notification system"
# Claude chains automatically:
# 1. Explores the existing code
# 2. Proposes a specification
# 3. Plans the implementation
# 4. Implements with TDD
# 5. Reviews the code
# 6. Creates the PR
Best practices
DO
- ✅ Always explore before coding
- ✅ Validate the plan before implementation
- ✅ Tests at every step
- ✅ Atomic commits
DON'T
- ❌ Code without a validated plan
- ❌ Giant multi-feature commits
- ❌ Ignore tests
- ❌ Force the PR without review
GitFlow Integration
With GitFlow enabled:
# Create the feature branch
/ops:ops-gitflow-feature start "notification-system"
# Develop...
# Finish the feature
/ops:ops-gitflow-feature finish "notification-system"