architect-systemlisted

Designs technical blueprints — tech stack selection, database schema, API design, file structure, and deployment plan for a defined product or feature. Produces `architecture/system-architecture.md`. Not for unclear requirements (use discover) or task decomposition (use breakdown-tasks). For user journey mapping, see map-user-flow. For code quality after building, see review-work.
hungv47/meta-skills · ★ 9 · AI & Automation · score 75

Install: claude install-skill hungv47/meta-skills

# System Architecture Designer — Orchestrator Transforms product specifications into a technical blueprint covering stack, schema, APIs, and deployment. Capability metadata (route triggers, prerequisites, load map, artifact contract) lives in [`routing.yaml`](routing.yaml). Methodology and history: [`references/playbook.md`](references/playbook.md). **Core question:** Will this still work at 10x scale with 10x team? ## When To Use - Defined product or feature needing a technical blueprint (stack, schema, API, infra, deployment). - Major scale shift (10x growth) or migration to new core infrastructure. - Greenfield, brownfield (extending existing system), or migration (replacing existing). - Architecture re-run after significant spec change. ## When NOT To Use - Requirements fuzzy → `/discover`. - Code-level cleanup → `/clean-code`. - Task decomposition from existing architecture → `/breakdown-tasks`. - UI/flow mapping → `/map-user-flow`. - Existing code has the same operational mechanics duplicated across 2+ callers → `/extract-service`. ## Before Starting | Artifact | Source | Required? | |---|---|---| | `research/product-context.md` | research-icp | Recommended — product dims, voice, constraints | | `.forsvn/artifacts/meta/specs/*.md` | spec/PRD | Recommended — feature scope | | `.forsvn/artifacts/product/flow/*.md` | map-user-flow | Recommended — user types + flows | | `.forsvn/experience/technical.md` | (any skill) | Optional — stack history + constraints | | `.fo