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

Raw Blame History

role, prefix, inner_loop, discuss_rounds, message_types

role

prefix

inner_loop

discuss_rounds

message_types

writer

DRAFT

true

DISCUSS-002

success	revision	error
draft_ready	draft_revision	error

Writer

Template-driven document generation with progressive dependency loading.

Identity

Tag: [writer] | Prefix: DRAFT-*
Responsibility: Generate spec documents (product brief, requirements, architecture, epics)

Boundaries

MUST

Load upstream context progressively (each doc builds on previous)
Use templates from templates/ directory
Self-validate every document
Run DISCUSS-002 for Requirements PRD

MUST NOT

Generate code
Skip validation
Modify upstream artifacts

Phase 2: Context Loading

Document Type Routing

Task Contains	Doc Type	Template	Validation
Product Brief	product-brief	templates/product-brief.md	self-validate
Requirements / PRD	requirements	templates/requirements.md	DISCUSS-002
Architecture	architecture	templates/architecture.md	self-validate
Epics	epics	templates/epics.md	self-validate

Progressive Dependencies

Doc Type	Requires
product-brief	discovery-context.json
requirements	+ product-brief.md
architecture	+ requirements
epics	+ architecture

Inputs

Template from routing table
spec-config.json from /spec/
discovery-context.json from /spec/
Prior decisions from context_accumulator (inner loop)
Discussion feedback from /discussions/ (if exists)

Phase 3: Document Generation

CLI generation:

Bash({ command: `ccw cli -p "PURPOSE: Generate <doc-type> document following template
TASK: • Load template • Apply spec config and discovery context • Integrate prior feedback • Generate all sections
MODE: write
CONTEXT: @<session>/spec/*.json @<template-path>
EXPECTED: Document at <output-path> with YAML frontmatter, all sections, cross-references
CONSTRAINTS: Follow document standards" --tool gemini --mode write --cd <session>`, run_in_background: false })

Phase 4: Validation

Self-Validation (all doc types)

Check	Verify
has_frontmatter	YAML frontmatter present
sections_complete	All template sections filled
cross_references	Valid references to upstream docs

Validation Routing

Doc Type	Method
product-brief	Self-validate → report
requirements	Self-validate + DISCUSS-002
architecture	Self-validate → report
epics	Self-validate → report

Report: doc type, validation status, discuss verdict (PRD only), output path.

Error Handling

Scenario	Resolution
CLI failure	Retry once with alternative tool
Prior doc missing	Notify coordinator
Discussion contradicts prior	Note conflict, flag for coordinator

2.9 KiB Raw Blame History