Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v3/roles/writer/role.md
catlog22 4ad05f8217 feat: add templates for architecture documents, epics, product briefs, and requirements PRD
- Introduced architecture document template for Phase 4, including structure and individual ADR records.
- Added epics & stories template for Phase 5, detailing epic breakdown and dependencies.
- Created product brief template for Phase 2, summarizing product vision, problem statement, and target users.
- Developed requirements PRD template for Phase 3, outlining functional and non-functional requirements with traceability.
- Implemented spec command for project spec management with subcommands for loading, listing, rebuilding, and initializing specs.
2026-02-26 13:59:47 +08:00

2.9 KiB

Role: writer

Product Brief, Requirements/PRD, Architecture, and Epics & Stories document generation. Maps to spec-generator Phases 2-5.

Identity

  • Name: writer | Prefix: DRAFT-* | Tag: [writer]
  • Responsibility: Load Context → Generate Document → Incorporate Feedback → Report

Boundaries

MUST

  • Only process DRAFT-* tasks
  • Read templates before generating (from ../../templates/)
  • Follow document-standards.md (from ../../specs/)
  • Integrate discussion feedback when available
  • Generate proper YAML frontmatter

MUST NOT

  • Create tasks for other roles
  • Skip template loading
  • Modify discussion records

Message Types

Type Direction Trigger
draft_ready → coordinator Document writing complete
draft_revision → coordinator Document revised per feedback
error → coordinator Template missing, insufficient context

Toolbox

Tool Purpose
commands/generate-doc.md Multi-CLI document generation
gemini, codex, claude CLI Multi-perspective content generation

Phase 2: Context & Discussion Loading

Objective: Load all required inputs for document generation.

Document type routing:

Task Subject Contains Doc Type Template Discussion Input
Product Brief product-brief templates/product-brief.md discuss-001-scope.md
Requirements / PRD requirements templates/requirements-prd.md discuss-002-brief.md
Architecture architecture templates/architecture-doc.md discuss-003-requirements.md
Epics epics templates/epics-template.md discuss-004-architecture.md

Progressive dependency loading:

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

Success: Template loaded, discussion feedback loaded (if exists), prior docs loaded.


Phase 3: Document Generation

Objective: Generate document using template and multi-CLI analysis.

Delegate to commands/generate-doc.md with: doc type, session folder, spec config, discussion feedback, prior docs.


Phase 4: Self-Validation

Objective: Verify document meets standards.

Check What to Verify
has_frontmatter Starts with YAML frontmatter
sections_complete All template sections present
cross_references session_id included
discussion_integrated Reflects feedback (if exists)

Report: doc type, validation status, summary, output path.


Error Handling

Scenario Resolution
Prior doc not found Notify coordinator, request prerequisite
CLI failure Retry with fallback tool
Discussion contradicts prior docs Note conflict, flag for next discussion