architecture-bootstraplisted

The ARCHITECTURE-phase author-side guide — the counterpart to design-bootstrap. architecture-validator VALIDATES docs/architecture.md but nothing authors it, so a greenfield ARCHITECTURE phase had no skill to produce the doc. This authors docs/architecture.md (logical/component architecture, data model, integration contracts, a domain-policy-aware security & privacy architecture, NFRs, deployment baseline) + one revisitable ADR per consequential decision, after ASKING the operator the technology/deployment baseline (propose sensible defaults / specify the stack / stack-agnostic). Then arms the consensus marker so architecture-validator + consensus review it. Use at the start of ARCHITECTURE.
mytechsonamy/VibeFlow · ★ 0 · AI & Automation · score 75

Install: claude install-skill mytechsonamy/VibeFlow

# Architecture Bootstrap ARCHITECTURE has the same gap DESIGN had before `design-bootstrap`: `architecture-validator` **validates** `docs/architecture.md` (its hard precondition is that the doc "must exist and be non-empty") but **nothing authors it**. On a greenfield project there's no architecture doc to validate, so the phase stalls. This skill authors it — and the consequential, expensive technology decisions get **asked**, never invented silently. ## Phase Contract Runs in **ARCHITECTURE** only. Before anything else, read `vibeflow.config.json`'s `currentPhase`. If it is not ARCHITECTURE, emit: > architecture-bootstrap is for the ARCHITECTURE phase only; current is > `<phase>`. Advance to ARCHITECTURE first (`/vibeflow:advance`). …and stop. Writes are confined to `docs/**`, `contracts/**`, `.vibeflow/reports/adr-*.md`, `*.d.ts`, `.vibeflow/**`, and `vibeflow.config.json` (the ARCHITECTURE phase-write policy). ## Step 1: Resolve context Read: - `vibeflow.config.json` → `domain`, `platform`, `riskTolerance`, `project`. - The **approved PRD** (REQUIREMENTS' primary) + `.vibeflow/reports/prd-quality-report.md` (the validator requires testability ≥ 60 — confirm it passed). - The **approved design** (`design/design-spec.md` from DESIGN) — the architecture must serve it. - Existing `docs/architecture.md` + `docs/adr/*.md` (re-runs refine, never clobber silently). - **Brownfield only:** the current import graph via `mcp__codebase-intel__ci_dependency_graph` / `ci_