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.
3.0 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | |
|---|---|---|---|---|
| executor | TDFIX | true |
|
Tech Debt Executor
Debt cleanup executor. Apply remediation plan actions in worktree: refactor code, update dependencies, add tests, add documentation. Batch-delegate to CLI tools, self-validate after each batch.
Phase 2: Load Remediation Plan
| Input | Source | Required |
|---|---|---|
| Session path | task description (regex: session:\s*(.+)) |
Yes |
| .msg/meta.json | /.msg/meta.json | Yes |
| Remediation plan | /plan/remediation-plan.json | Yes |
| Worktree info | meta.json:worktree.path, worktree.branch | Yes |
| Context accumulator | From prior TDFIX tasks (inner loop) | Yes (inner loop) |
- Extract session path from task description
- Read .msg/meta.json for worktree path and branch
- Read remediation-plan.json, extract all actions from plan phases
- Group actions by type: refactor, restructure, add-tests, update-deps, add-docs
- Split large groups (> 10 items) into sub-batches of 10
- For inner loop (fix-verify cycle): load context_accumulator from prior TDFIX tasks, parse review/validation feedback for specific issues
Batch order: refactor -> update-deps -> add-tests -> add-docs -> restructure
Phase 3: Execute Fixes
For each batch, use CLI tool for implementation:
Worktree constraint: ALL file operations and commands must execute within worktree path. Use cd "<worktree-path>" && ... prefix for all Bash commands.
Per-batch delegation:
ccw cli -p "PURPOSE: Apply tech debt fixes in batch; success = all items fixed without breaking changes
TASK: <batch-type-specific-tasks>
MODE: write
CONTEXT: @<worktree-path>/**/* | Memory: Remediation plan context
EXPECTED: Code changes that fix debt items, maintain backward compatibility, pass existing tests
CONSTRAINTS: Minimal changes only | No new features | No suppressions | Read files before modifying
Batch type: <refactor|update-deps|add-tests|add-docs|restructure>
Items: <list-of-items-with-file-paths-and-descriptions>" --tool gemini --mode write --cd "<worktree-path>"
Wait for CLI completion before proceeding to next batch.
Fix Results Tracking:
| Field | Description |
|---|---|
| items_fixed | Count of successfully fixed items |
| items_failed | Count of failed items |
| items_remaining | Remaining items count |
| batches_completed | Completed batch count |
| files_modified | Array of modified file paths |
| errors | Array of error messages |
After each batch, verify file modifications via git diff --name-only in worktree.
Phase 4: Self-Validation
All commands in worktree:
| Check | Command | Pass Criteria |
|---|---|---|
| Syntax | tsc --noEmit or python -m py_compile |
No new errors |
| Lint | eslint --no-error-on-unmatched-pattern |
No new errors |
Write <session>/fixes/fix-log.json with fix results. Update .msg/meta.json with fix_results.
Append to context_accumulator for next TDFIX task (inner loop): files modified, fixes applied, validation results, discovered caveats.