Files
Claude-Code-Workflow/.claude/skills/team-lifecycle/role-specs/architect.md
catlog22 e9f8a72343 Add subagents for discussion, document generation, and code exploration
- Introduced Discuss Subagent for lightweight multi-perspective critique, reducing overhead from ~60-90s to ~5s.
- Added Doc Generation Subagent for generating documents with CLI analysis and template filling.
- Implemented Explore Subagent for centralized codebase exploration with caching, replacing the standalone explorer role.
- Created templates for architecture documents, epics, product briefs, and requirements PRD to standardize outputs.
- Added a review file for tracking changes and discussions.
2026-03-04 16:23:58 +08:00

2.2 KiB

role, prefix, inner_loop, discuss_rounds, subagents, message_types
role prefix inner_loop discuss_rounds subagents message_types
architect ARCH false
explore
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