mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-05 16:13:08 +08:00

Files

catlog22 bbdd1840de Add document standards, quality gates, and templates for team lifecycle phases

- Introduced `document-standards.md` to define YAML frontmatter schema, naming conventions, and content structure for spec-generator outputs.
- Created `quality-gates.md` outlining per-phase quality gate criteria and scoring dimensions for spec-generator outputs.
- Added templates for architecture documents, epics and stories, product briefs, and requirements PRD to streamline documentation in respective phases.

2026-03-04 23:54:20 +08:00

3.6 KiB

Raw Blame History

role, prefix, inner_loop, discuss_rounds, cli_tools, message_types

role

prefix

inner_loop

discuss_rounds

cli_tools

message_types

analyst

RESEARCH

false

DISCUSS-001

discuss

success	progress	error
research_ready	research_progress	error

Analyst — Phase 2-4

Phase 2: Seed Analysis

Objective: Extract structured seed information from the topic/idea.

Extract session folder from task description (Session: <path>)
Parse topic from task description (first non-metadata line)
If topic starts with @ or ends with .md/.txt → Read the referenced file as topic content
Run Gemini CLI seed analysis:

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

Wait for CLI result, parse seed analysis JSON

Phase 3: Codebase Exploration (conditional)

Objective: Gather codebase context if an existing project is detected.

Condition	Action
package.json / Cargo.toml / pyproject.toml / go.mod exists	Explore codebase
No project files	Skip → codebase context = null

When project detected: Use CLI exploration with Gemini.

Bash({
  command: `ccw cli -p "PURPOSE: Explore codebase for general context to inform spec generation
TASK: • Identify tech stack and frameworks • Map architecture patterns • Document conventions • List integration points
MODE: analysis
CONTEXT: @**/* | Memory: Seed analysis keywords: <keywords>
EXPECTED: JSON with: tech_stack[], architecture_patterns[], conventions[], integration_points[]
CONSTRAINTS: Focus on general context" --tool gemini --mode analysis --rule analysis-analyze-code-patterns`,
  run_in_background: false
})

Parse CLI output to build codebase context: tech_stack, architecture_patterns, conventions, integration_points.

Phase 4: Context Packaging + Inline Discuss

4a: Context Packaging

spec-config.json → <session-folder>/spec/spec-config.json:

session_id, topic, status="research_complete", complexity, depth, focus_areas, mode="interactive"

discovery-context.json → <session-folder>/spec/discovery-context.json:

session_id, phase=1, seed_analysis (all fields), codebase_context (or null), recommendations

design-intelligence.json → <session-folder>/analysis/design-intelligence.json (UI mode only):

Produced when frontend keywords detected in seed_analysis
Fields: industry, style_direction, ux_patterns, color_strategy, typography, component_patterns

4b: Inline Discuss (DISCUSS-001)

Invoke multi-perspective discussion using CLI tools:

Artifact: <session-folder>/spec/discovery-context.json
Round: DISCUSS-001
Perspectives: product, risk, coverage

Handle discuss verdict per team-worker consensus handling protocol.

Report: complexity, codebase presence, problem statement, exploration dimensions, discuss verdict + severity, output paths.

Error Handling

Scenario	Resolution
Gemini CLI failure	Fallback to direct Claude analysis
Codebase detection failed	Continue as new project
Topic too vague	Report with clarification questions
CLI exploration fails	Continue without codebase context
Multi-perspective discussion fails	Proceed without discuss, log warning

3.6 KiB Raw Blame History