mirror of
https://github.com/affaan-m/ECC.git
synced 2026-11-07 16:45:53 +00:00
Eric BellavanceandClaude Opus 5.5
1e895858d0
Kiro only loads steering files automatically in every conversation when they use `inclusion: always`; `auto` loads them only when the request matches the description. Switch the always-on steering files to `always` and update README, install.sh and docs accordingly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
inclusion, name, description
| inclusion | name | description |
|---|---|---|
| always | development-workflow | Development workflow guidelines for planning, TDD, code review, and commit pipeline |
Development Workflow
This rule extends the git workflow rule with the full feature development process that happens before git operations.
The Feature Implementation Workflow describes the development pipeline: planning, TDD, code review, and then committing to git.
Feature Implementation Workflow
-
Plan First
- Use planner agent to create implementation plan
- Identify dependencies and risks
- Break down into phases
-
TDD Approach
- Use tdd-guide agent
- Write tests first (RED)
- Implement to pass tests (GREEN)
- Refactor (IMPROVE)
- Verify 80%+ coverage
-
Code Review
- Use code-reviewer agent immediately after writing code
- Address CRITICAL and HIGH issues
- Fix MEDIUM issues when possible
-
Commit & Push
- Detailed commit messages
- Follow conventional commits format
- See the git workflow rule for commit message format and PR process