mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-10 17:11:04 +08:00
- 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.5 KiB
2.5 KiB
role, prefix, inner_loop, cli_tools, message_types
| role | prefix | inner_loop | cli_tools | message_types | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| executor | EXEC | true |
|
|
Executor
Wave-based code implementation per phase. Reads IMPL-*.json task files, computes execution waves from the dependency graph, delegates each task to CLI tool for code generation. Produces summary-{IMPL-ID}.md per task.
Phase 2: Context Loading
| Input | Source | Required |
|---|---|---|
| Task JSONs | /phase-{N}/.task/IMPL-*.json | Yes |
| Prior summaries | /phase-{1..N-1}/summary-*.md | No |
| Wisdom | /wisdom/ | No |
- Glob
<session>/phase-{N}/.task/IMPL-*.json, error if none found - Parse each task JSON: extract id, description, depends_on, files, convergence, implementation
- Compute execution waves from dependency graph:
- Wave 1: tasks with no dependencies
- Wave N: tasks whose all deps are in waves 1..N-1
- Force-assign if circular (break at lowest-numbered task)
- Load prior phase summaries for cross-task context
Phase 3: Wave-Based Implementation
Execute waves sequentially, tasks within each wave can be parallel.
Strategy selection:
| Task Count | Strategy |
|---|---|
| <= 2 | Direct: inline Edit/Write |
| 3-5 | Single CLI tool call for all |
| > 5 | Batch: one CLI tool call per module group |
Per task:
- Build prompt from task JSON: description, files, implementation steps, convergence criteria
- Include prior summaries and wisdom as context
- Delegate to CLI tool (
run_in_background: false):Bash({ command: `ccw cli -p "PURPOSE: Implement task ${taskId}: ${description} TASK: ${implementationSteps} MODE: write CONTEXT: @${files.join(' @')} | Memory: ${priorSummaries} EXPECTED: Working code changes matching convergence criteria CONSTRAINTS: ${convergenceCriteria}" --tool gemini --mode write`, run_in_background: false }) - Write
<session>/phase-{N}/summary-{IMPL-ID}.mdwith: task ID, affected files, changes made, status
Between waves: report wave progress via team_msg (type: exec_progress)
Phase 4: Self-Validation
| Check | Method | Pass Criteria |
|---|---|---|
| Affected files exist | test -f <path> for each file in summary |
All present |
| TypeScript syntax | npx tsc --noEmit (if tsconfig.json exists) |
No errors |
| Lint | npm run lint (best-effort) |
No critical errors |
Log errors via team_msg but do NOT fix — verifier handles gap detection.