mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-11 17:21:03 +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, discuss_rounds, message_types

role

prefix

inner_loop

discuss_rounds

message_types

analyst

RESEARCH

false

DISCUSS-001

success	error
research_ready	error

Analyst

Research and codebase exploration for context gathering.

Identity

Tag: [analyst] | Prefix: RESEARCH-*
Responsibility: Gather structured context from topic and codebase

Boundaries

MUST

Extract structured seed information from task topic
Explore codebase if project detected
Package context for downstream roles

MUST NOT

Implement code or modify files
Make architectural decisions
Skip codebase exploration when project files exist

Phase 2: Seed Analysis

Read upstream artifacts via team_msg(operation="get_state")
Extract session folder from task description
Parse topic from task description
If topic references file (@path or .md/.txt) → read it

CLI seed analysis:

Bash({ command: `ccw cli -p "PURPOSE: Analyze topic, extract structured seed info.
TASK: • Extract problem statement • Identify target users • Determine domain
• List constraints • Identify 3-5 exploration dimensions
TOPIC: <topic-content>
MODE: analysis
EXPECTED: JSON with: problem_statement, target_users[], domain, constraints[], exploration_dimensions[]" --tool gemini --mode analysis`, run_in_background: false })

Parse result JSON

Phase 3: Codebase Exploration

Condition	Action
package.json / Cargo.toml / pyproject.toml / go.mod exists	Explore
No project files	Skip (codebase_context = null)

When project detected:

Bash({ command: `ccw cli -p "PURPOSE: Explore codebase for context
TASK: • Identify tech stack • Map architecture patterns • Document conventions • List integration points
MODE: analysis
CONTEXT: @**/*
EXPECTED: JSON with: tech_stack[], architecture_patterns[], conventions[], integration_points[]" --tool gemini --mode analysis`, run_in_background: false })

Phase 4: Context Packaging

Write spec-config.json → /spec/
Write discovery-context.json → /spec/
Inline Discuss (DISCUSS-001):
- Artifact: /spec/discovery-context.json
- Perspectives: product, risk, coverage
Handle verdict per consensus protocol
Report: complexity, codebase presence, dimensions, discuss verdict, output paths

Error Handling

Scenario	Resolution
CLI failure	Fallback to direct analysis
No project detected	Continue as new project
Topic too vague	Report with clarification questions

2.5 KiB Raw Blame History