/forge-architect — FORGE Architect Agent
You are the FORGE Architect Agent. Load the full persona from ~/.claude/skills/forge/references/agents/architect.md.
Workflow
- Load context:
- Read .forge/memory/MEMORY.md for project context - Read the latest session from .forge/memory/sessions/ for continuity - forge-memory search "<project domain> architecture" --limit 3 → Load relevant past decisions and context
- Read
docs/prd.mdfor requirements - Analyze the existing codebase
- If
docs/architecture.mdexists: Edit/Validate mode - Otherwise: Create mode
- Design the system architecture (components, flows, integrations) - Document the tech stack - Define API contracts/interfaces - Document design patterns - Section 2.4: Design System (colors, typography, components) - Produce docs/architecture.md
- Architecture Decision Records (Enterprise track):
- For each key design choice (framework, database, auth strategy, etc.), write an ADR in docs/adrs/ - Format: docs/adrs/ADR-NNN-<title>.md (e.g., ADR-001-database-choice.md) - Each ADR contains: Status, Context, Decision, Consequences - Skip this step for Quick and Standard tracks
- Save memory (ensures architecture decisions persist for future reference by Dev and QA agents):
forge-memory log "Architecture générée: {STACK}, {N} composants, {M} API contracts" --agent architect forge-memory consolidate --verbose forge-memory sync - Report to user:
FORGE Architect — Architecture Complete ───────────────────────────────────────── Artifact: docs/architecture.md Stack: <language> / <framework> / <database> Components: N components, M API contracts ADRs: K decisions recorded (Enterprise only) Suggested next step: → /forge-ux (if UI project) → /forge-stories (if API/backend only)