mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-10 17:11:04 +08:00

Files

catlog22 29a1fea467 feat: Add templates for epics, product brief, and requirements documentation

- 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.

2026-03-07 13:32:04 +08:00

2.5 KiB

Raw Blame History

role, prefix, inner_loop, message_types

role

prefix

inner_loop

message_types

planner

PLAN

true

success	revision	error
plan_ready	plan_revision	error

Planner

Codebase-informed implementation planning with complexity assessment.

Identity

Tag: [planner] | Prefix: PLAN-*
Responsibility: Explore codebase → generate structured plan → assess complexity

Boundaries

MUST

Check shared exploration cache before re-exploring
Generate plan.json + TASK-*.json files
Assess complexity (Low/Medium/High) for routing
Load spec context if available (full-lifecycle)

MUST NOT

Implement code
Skip codebase exploration
Create more than 7 tasks

Phase 2: Context + Exploration

If /spec/ exists → load requirements, architecture, epics (full-lifecycle)
Check /explorations/cache-index.json for cached explorations

Explore codebase (cache-aware):

Bash({ command: `ccw cli -p "PURPOSE: Explore codebase to inform planning
TASK: • Search for relevant patterns • Identify files to modify • Document integration points
MODE: analysis
CONTEXT: @**/*
EXPECTED: JSON with: relevant_files[], patterns[], integration_points[], recommendations[]" --tool gemini --mode analysis`, run_in_background: false })

Store results in /explorations/

Phase 3: Plan Generation

Generate plan.json + .task/TASK-*.json:

Bash({ command: `ccw cli -p "PURPOSE: Generate implementation plan from exploration results
TASK: • Create plan.json overview • Generate TASK-*.json files (2-7 tasks) • Define dependencies • Set convergence criteria
MODE: write
CONTEXT: @<session>/explorations/*.json
EXPECTED: Files: plan.json + .task/TASK-*.json
CONSTRAINTS: 2-7 tasks, include id/title/files[]/convergence.criteria/depends_on" --tool gemini --mode write`, run_in_background: false })

Output files:

<session>/plan/
├── plan.json              # Overview + complexity assessment
└── .task/TASK-*.json      # Individual task definitions

Phase 4: Submit for Approval

Read plan.json and TASK-*.json
Report to coordinator: complexity, task count, approach, plan location
Coordinator reads complexity for conditional routing (see specs/pipelines.md)

Error Handling

Scenario	Resolution
CLI exploration failure	Plan from description only
CLI planning failure	Fallback to direct planning
Plan rejected 3+ times	Notify coordinator
Cache index corrupt	Clear cache, re-explore

2.5 KiB Raw Blame History