Offer Solo Mode as default agent architecture

[jkleske]

Priority: P2

Problem

The current architecture defines 5 lifecycle agents in .claude/agents/:

Agent	Role	Lifecycle
HORIZON	Strategy	v0.1-v0.5
STUDIO	Design	v0.3-v0.6
WERK	Build	v0.6-v0.8
METRO	Ops	v0.9-v1.0
DEVLAB	Technical specialist	v0.6-v0.8 (overlaps WERK)

Note: PR #50 already proposes merging DEVLAB into WERK due to scope overlap.

For most users — especially solo developers or small teams building their first product with this template — the multi-agent Team Mode is premature complexity:

1. Cognitive overhead — understanding which agent handles which gate requires reading all 5 agent files
2. Handoff friction — inter-agent collaboration rules (HORIZON↔STUDIO at v0.4, STUDIO↔WERK at v0.6) add ceremony without benefit for solo use
3. Context fragmentation — each agent loads only its own context, losing cross-phase insights

Most users will be a single person running Claude Code in a single terminal. They need one agent that adapts to the current PRD gate.

Proposed Change

Add a product-agent as the default Solo Mode agent:

# .claude/agents/product-agent.md
name: product-agent
description: "Solo product development agent. Reads current PRD version and activates relevant gate skills automatically."

The product-agent should:

1. Read PRD.md metadata to determine current gate (v0.X)
2. Activate the corresponding gate skill (e.g., prd-commercial for v0.3) — see Consolidate 31 skills to ~10 gate-transition skills #54 for skill consolidation
3. Know all ID prefixes from domain-profile.yaml
4. Have full tool access (Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch)

Keep lifecycle agents as opt-in Team Mode:

• Move HORIZON, STUDIO, WERK, METRO to .claude/agents/team/ subdirectory (or document as "Team Mode" in .claude/README.md)
• Users who want multi-agent orchestration can explicitly invoke them

Update .claude/README.md (agent index) to present Solo Mode as default:

## Solo Mode (Default)
- `product-agent` — single agent for all gates, auto-adapts to PRD version

## Team Mode (Advanced)
- `horizon` — Strategy (v0.1-v0.5)
- `studio` — Design (v0.3-v0.6)
- `werk` — Build (v0.6-v0.8)
- `metro` — Ops (v0.9-v1.0)

Files to Change

File	Change
.claude/agents/product-agent.md	New. Solo agent that reads PRD version and activates gate skills
.claude/agents/team/	New directory. Move horizon.md, studio.md, werk.md, metro.md here
.claude/README.md	Update agent index: Solo Mode (default) + Team Mode (advanced)
.claude/domain-profile.yaml	Add product-agent to agent registry, mark lifecycle agents as mode: team

Acceptance Criteria

• .claude/agents/product-agent.md exists and includes gate-detection logic
• product-agent references domain-profile.yaml for ID prefixes
• product-agent has full tool access (Read, Write, Edit, Bash, etc.)
• Lifecycle agents still work when explicitly invoked (no breaking changes)
• .claude/README.md documents both modes with Solo as default
• DEVLAB is removed or merged per PR fix: merge DEVLAB agent into WERK, remove duplicate #50 before this change

Verification

1. In a fresh project, run /product-agent — it should detect the PRD version and suggest the appropriate gate skill
2. Lifecycle agents in team/ can still be invoked explicitly
3. domain-profile.yaml validates: python3 -c "import yaml; yaml.safe_load(open('.claude/domain-profile.yaml'))"

Related

• PR fix: merge DEVLAB agent into WERK, remove duplicate #50 — Merge DEVLAB into WERK (prerequisite: removes the duplicate agent)
• Issue Consolidate 31 skills to ~10 gate-transition skills #54 — Skill consolidation (the gate skills that product-agent would activate)