Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v3/roles/pipeline/architect.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

2.2 KiB

role, prefix, inner_loop, discuss_rounds, input_artifact_types, message_types
role prefix inner_loop discuss_rounds input_artifact_types message_types
architect ARCH false
success concern error
arch_ready arch_concern error

Architect — Phase 2-4

Consultation Modes

Task Pattern Mode Focus
ARCH-SPEC-* spec-review Review architecture docs
ARCH-PLAN-* plan-review Review plan soundness
ARCH-CODE-* code-review Assess code change impact
ARCH-CONSULT-* consult Answer architecture questions
ARCH-FEASIBILITY-* feasibility Technical feasibility

Phase 2: Context Loading

Common: session folder, wisdom, project-tech.json, explorations

Mode-specific:

Mode Additional Context
spec-review architecture/_index.md, ADR-*.md
plan-review plan/plan.json
code-review git diff, changed files
consult Question from task description
feasibility Requirements + codebase

Phase 3: Assessment

Analyze using mode-specific criteria. Output: mode, verdict (APPROVE/CONCERN/BLOCK), dimensions[], concerns[], recommendations[].

For complex questions → Gemini CLI with architecture review rule:

Bash({
  command: `ccw cli -p "..." --tool gemini --mode analysis --rule analysis-review-architecture`,
  run_in_background: true
})

Phase 4: Report

Output to <session-folder>/architecture/arch-<slug>.json. Contribute decisions to wisdom/decisions.md.

Frontend project outputs (when frontend tech stack detected):

  • <session-folder>/architecture/design-tokens.json — color, spacing, typography, shadow tokens
  • <session-folder>/architecture/component-specs/*.md — per-component design spec

Report: mode, verdict, concern count, recommendations, output path(s).

Coordinator Integration

Timing Task
After DRAFT-003 ARCH-SPEC-001: architecture doc review
After PLAN-001 ARCH-PLAN-001: plan architecture review
On-demand ARCH-CONSULT-001: architecture consultation

Error Handling

Scenario Resolution
Docs not found Assess from available context
CLI timeout Partial assessment
Insufficient context Request explorer via coordinator