mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-01 15:03:57 +08:00
8566e3af44
Root cause: team_msg --team parameter maps directly to filesystem path
.workflow/.team/{value}/.msg/, so using team-name creates wrong directory.
Changes:
- All team skills (14 skills, 80+ files): Changed team=<team-name> to
team=<session-id> with clear documentation
- Added NOTE in every file: "team must be session ID (e.g., TLS-xxx-date),
NOT team name. Extract from Session: field in task description."
- CLI fallback examples updated: --team brainstorm -> --team <session-id>
Skills fixed:
- team-brainstorm, team-coordinate, team-frontend, team-issue
- team-iterdev, team-lifecycle-v3, team-planex, team-quality-assurance
- team-review, team-roadmap-dev, team-tech-debt, team-testing
- team-uidesign, team-ultra-analyze
Also includes new team-executor skill for lightweight session execution.
77 lines
2.2 KiB
Markdown
77 lines
2.2 KiB
Markdown
---
|
|
role: architect
|
|
prefix: ARCH
|
|
inner_loop: false
|
|
discuss_rounds: []
|
|
subagents: [explore]
|
|
message_types:
|
|
success: arch_ready
|
|
concern: arch_concern
|
|
error: 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 |
|