mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-07 16:41:06 +08:00
3fd55ebd4b
- Introduced Role Analysis Reviewer Agent to validate role analysis outputs against templates and quality standards. - Created a detailed validation ruleset for the system-architect role, including mandatory and recommended sections. - Added JSON validation report structure for output. - Implemented execution command for validation process. test: Add UX tests for HookCard component - Created comprehensive tests for HookCard component, focusing on delete confirmation UX pattern. - Verified confirmation dialog appearance, deletion functionality, and button interactions. - Ensured proper handling of state updates and visual feedback for enabled/disabled status. test: Add UX tests for ThemeSelector component - Developed tests for ThemeSelector component, emphasizing delete confirmation UX pattern. - Validated confirmation dialog display, deletion actions, and toast notifications for undo functionality. - Ensured proper management of theme slots and state updates. feat: Implement useDebounce hook - Added useDebounce hook to delay expensive computations or API calls, enhancing performance. feat: Create System Architect Analysis Template - Developed a comprehensive template for system architect role analysis, covering required sections such as architecture overview, data model, state machine, error handling strategy, observability requirements, configuration model, and boundary scenarios. - Included examples and templates for each section to guide users in producing SPEC.md-level precision modeling.
2.1 KiB
2.1 KiB
Templates Directory
This directory contains document templates used by workers during execution.
Available Templates
| Template | Used By | Task | Purpose |
|---|---|---|---|
| product-brief.md | writer | DRAFT-001 | Product vision and high-level requirements |
| requirements-prd.md | writer | DRAFT-002 | Detailed product requirements document |
| architecture-doc.md | writer | DRAFT-003 | System architecture and design decisions |
| epics-template.md | writer | DRAFT-004 | Epic breakdown and user stories |
Template Structure
All templates follow this structure:
---
title: <Document Title>
type: <product-brief|requirements|architecture|epics>
version: 1.0
created: <ISO8601 timestamp>
author: <role-name>
---
# <Document Title>
## Section 1
...
## Section 2
...
Usage
By Workers
Workers load templates during Phase 3 (Domain Work):
- Read template file
- Fill in sections based on research/context
- Generate artifact with proper frontmatter
- Create artifact manifest
By Coordinator
Coordinator references templates when creating tasks:
- DRAFT-001 →
product-brief.md - DRAFT-002 →
requirements-prd.md - DRAFT-003 →
architecture-doc.md - DRAFT-004 →
epics-template.md
Template Customization
To customize templates:
- Modify template files in this directory
- Ensure YAML frontmatter structure is preserved
- Update section headings as needed
- Test with a sample task
Document Standards
All generated documents must follow:
- Formatting: See ../specs/document-standards.md
- Quality criteria: See ../specs/quality-gates.md
- Artifact contract: See ../specs/artifact-contract-spec.md
Cross-References
- Specifications: See ../specs/README.md
- Role specifications: See ../roles/README.md
- Writer role: See ../roles/pipeline/writer.md
- Main entry: See ../SKILL.md