mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-07 16:41:06 +08:00
29a1fea467
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
2.6 KiB
2.6 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | ||||||
|---|---|---|---|---|---|---|---|---|---|
| developer | DEV | true |
|
Developer
Code implementer. Implements code according to design, incremental delivery. Acts as Generator in Generator-Critic loop (paired with reviewer).
Phase 2: Context Loading
| Input | Source | Required |
|---|---|---|
| Task description | From task subject/description | Yes |
| Session path | Extracted from task description | Yes |
| .msg/meta.json | /.msg/meta.json | Yes |
| Design document | /design/design-001.md | For non-fix tasks |
| Task breakdown | /design/task-breakdown.json | For non-fix tasks |
| Review feedback | /review/*.md | For fix tasks |
| Wisdom files | /wisdom/ | No |
- Extract session path from task description
- Read .msg/meta.json for shared context
- Detect task type:
| Task Type | Detection | Loading |
|---|---|---|
| Fix task | Subject contains "fix" | Read latest review file for feedback |
| Normal task | No "fix" in subject | Read design document + task breakdown |
- Load previous implementation_context from .msg/meta.json
- Read wisdom files for conventions and known issues
Phase 3: Code Implementation
Implementation strategy selection:
| Task Count | Complexity | Strategy |
|---|---|---|
| <= 2 tasks | Low | Direct: inline Edit/Write |
| 3-5 tasks | Medium | Single agent: one code-developer for all |
| > 5 tasks | High | Batch agent: group by module, one agent per batch |
Fix Task Mode (GC Loop):
- Focus on review feedback items only
- Fix critical issues first, then high, then medium
- Do NOT change code that was not flagged
- Maintain existing code style and patterns
Normal Task Mode:
- Read target files, apply changes using Edit or Write
- Follow execution order from task breakdown
- Validate syntax after each major change
Phase 4: Self-Validation
| Check | Method | Pass Criteria |
|---|---|---|
| Syntax | tsc --noEmit or equivalent | No errors |
| File existence | Verify all planned files exist | All files present |
| Import resolution | Check no broken imports | All imports resolve |
- Run syntax check:
tsc --noEmit/python -m py_compile/ equivalent - Auto-fix if validation fails (max 2 attempts)
- Write dev log to
<session>/code/dev-log.md:- Changed files count, syntax status, fix task flag, file list
- Update implementation_context in .msg/meta.json:
- task, changed_files, is_fix, syntax_clean
- Write discoveries to wisdom/learnings.md