Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v3/specs/README.md
catlog22 3fd55ebd4b feat: Add Role Analysis Reviewer Agent and validation template
- 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.
2026-03-05 19:58:10 +08:00

3.1 KiB

Specifications Directory

This directory contains all specification documents for Team Lifecycle v3.

Core Specifications (Mandatory Reading)

Document Purpose When to Read
core-concepts.md Foundational principles: team-worker architecture, artifact contracts, quality gating, dynamic role injection, priority scheduling Before using the skill - P0 Critical
domain-model.md Core entity definitions (Task, Artifact, Role, Session) with JSON schemas, relationships, and state machines Before using the skill - P0 Critical
artifact-contract-spec.md Artifact manifest schema and validation rules Before using the skill - P0 Critical
execution-flow.md End-to-end execution walkthrough with pipeline definitions, beat cycle, conditional routing, and examples When understanding workflow - P1 High

Supporting Specifications

Document Purpose When to Read
quality-gates.md Quality validation criteria for each phase When reviewing quality checkpoints
document-standards.md Document formatting standards (YAML frontmatter, naming conventions) When creating new documents
team-config.json Role registry and pipeline definitions (machine-readable) When modifying role configuration

Document Hierarchy

specs/
├── README.md                       # This file
├── core-concepts.md                # P0 - Foundational principles
├── artifact-contract-spec.md       # P0 - Artifact manifest schema
├── execution-flow.md               # P1 - Execution walkthrough
├── quality-gates.md                # Supporting - Quality criteria
├── document-standards.md           # Supporting - Formatting standards
└── team-config.json                # Supporting - Role registry

Reading Path

For New Users

  1. Start here: core-concepts.md - Understand the system architecture and principles
  2. Then read: artifact-contract-spec.md - Learn how artifacts flow between agents
  3. Finally read: execution-flow.md - See how tasks execute end-to-end

For Developers Extending the Skill

  1. Read all core specifications above
  2. Review quality-gates.md for validation logic
  3. Review document-standards.md for formatting rules
  4. Modify team-config.json for role changes

For Troubleshooting

  1. Check execution-flow.md for pipeline definitions
  2. Check artifact-contract-spec.md for validation rules
  3. Check quality-gates.md for quality criteria

Cross-References