implement

Architecture Designer — Implementation Workflow

This skill turns an approved architecture document into a working project skeleton: data models, API stubs, configuration files, and infrastructure files. It always proposes a folder structure first and waits for the user's confirmation before writing any files.

Scripts and shared-reference paths: this file has no references/ of its own and points into the sibling design skill's references/ directory throughout (first used just below, in "Before starting"). See "Path resolution" at the bottom of this file for how both <scripts_dir> and design/references/... paths resolve.

---

Before starting — session completeness gate

Check for docs/architecture-designer/session.json:

• If the file exists: read it in full, then run python3 <scripts_dir>/validate-session.py and show its output — this is a hard gate; do not proceed to Step 1 until it reports SESSION CHECK PASSED. See design/references/session-schema.md section "Session completeness gate" for what the script checks, how to resolve a failure, and why this gate applies to implement even though its steps mostly work from the confirmed architecture document rather than the session stages directly. Reading it in full here (rather than only running the validator) is what makes its stage5 object available as a cross-check for Step 3's "Technology stack" input — the architecture document itself is that input's primary source, not stage5 (see Step 3 for why).
• If the file does not exist: this gate only applies when session.json exists — proceed without it. The architecture document confirmed in Step 1 is the authoritative source of truth for implementation in that case.

---

Step 1 — Find the architecture document

Check for an architecture document path in this order:

1. docs/architecture-designer/session.json — if it exists and contains a documents array, use its last entry (the most recently saved document) — the authoritative location when this skill follows a design session in the same working directory. If that path doesn't resolve to an existing file (moved or deleted since), fall back to option 2, not directly to option 3 — a stale recorded path doesn't mean no path is available; the current conversation may still hold the correct one.
2. Current conversation context — if the user just completed a /architecture-designer:design or /architecture-designer:review session and the document path is visible in the conversation.
3. Manual selection — if neither above yields a path, proceed to list files as described below.