Flow Architecture

Foundation sub-skill for the flow-architecture plugin (implements CDR-023). Runs at the start of every FDA orchestrator (`/flow:start-project`, `/flow:retrofit-project`, `/flow:add-domain`, `/flow:add-sub-flow`, `/flow:audit`) to verify the environment, discover existing FDA artifacts on the filesystem, classify the run mode, confirm Linear scope (writing `.flow/config.json` on first run via the embedded Q36 7-step bootstrap), and emit the Q12.5 structured preamble that downstream sub-skills consume. Read-only EXCEPT the atomic-rename `.flow/config.json` write on first successful confirmation or stale-config replacement.

Lightweight inventory append sub-skill for the flow-architecture plugin (implements CDR-023). Two modes — sub-flow-add (append one new flow row under an existing domain) and domain-add (append a fresh domain section via Q19-mini interview). Append-only semantics; never rewrites existing rows; never renames IDs. Triggered by `/flow:add-sub-flow` and `/flow:add-domain`. Sub-flow-add ~30s, domain-add ~5-10 min (interview-paced). Hard-rejects duplicates; sets a state flag for downstream regen-index dispatch.

Per-domain journey doc authoring sub-skill for the flow-architecture plugin (implements CDR-023). Writes ONE markdown file at `docs/product/journeys/<domain>.md` per domain, conforming to the Q26 locked template (variable phase count per Q26 mod 5; ~290-450+ lines based on TEAM precedent). Hybrid authoring — deterministic frontmatter stamping via the extracted `scripts/build_journey_frontmatter.py` builder (scaffold-log frontmatter + story-doc aggregation per ADR-033, fixture-locked); single body-only `Agent(journey-doc-author)` call for 7-9 narrative sections (single-agent preserves cross-phase narrative continuity). Runs AFTER `flow-doc-author` so story docs are available as authoring context AND as the personas/flow_ids aggregation source. 1 agent per domain; parallel across domains for multi-domain scaffolds with a concurrency cap of ~10 to avoid Claude Code background-agent queueing. 0 synchronous gates in default mode. Per-domain footprint ~90s; wall time scales as `ceil(N/10) * ~90s` — N≤10 domains fin

Heaviest-mutation sub-skill for the flow-architecture plugin (implements CDR-023). Writes per-domain Linear scaffolding — 1 milestone + N sub-flow parent issues + 5N discipline children + N Children-summary comments + 1 milestone description refresh = 2+7N writes per domain. Per-sub-flow execution unit, per-domain preview/approval. 3-layer idempotency (`.flow/scaffold-log/<domain>.md` append-only + per-sub-flow `list_issues` lookup + MCP error row flag). 100% per-issue fidelity-review coverage via background `Agent(general-purpose)` dispatch with sub-flow-boundary collection (every 6 issues). 1 mandatory pre-scaffold preview gate; conditional gates for failure recovery only. Sub-flow-atomic classified retry on failure (transient -> 1 retry + 2s backoff; permanent -> AskUserQuestion; cascading -> permanent + abort). Preview budget `(2+7N) × 500ms` -> N=10 ~36s, N=30 ~106s.

Greenfield Socratic inventory generator for the flow-architecture plugin (implements CDR-023). Output `docs/product/master-flow-inventory.md` populated with proposed domains + flows. Triggered by `/flow:start-project` (or standalone `/flow:inventory`) when `flow-preflight` mode classifier returns `greenfield`. Five phases — Phase 0 (PROJECT-INTENT priority filter) -> Phase 1 (app-classifier interview, shared with Q11 retrofit) -> Phase 2 (pattern-driven candidate generation, shared) -> skip Phase 3 (no code) -> Phase 4 (greenfield synthesis with 3-tag scope-priority) -> Phase 5 (user confirmation, shared). Per-run footprint ~10-30 min end-to-end (mostly user time).

Retrofit-mode inventory generator for the flow-architecture plugin (implements CDR-023). Mines code signals (routes, server actions, dialogs, menu items, API endpoints) from an existing Next.js App Router codebase and synthesizes the proposed inventory. Six phases — Phase 0 (PROJECT-INTENT priority filter) -> Phase 1 (app-classifier interview, shared with Q19 greenfield) -> Phase 2 (pattern-driven candidates, shared) -> Phase 3 (deterministic code scan, retrofit-only) -> Phase 4 (synthesis with 4-tag implementation-status taxonomy + value-priority) -> Phase 5 (user confirmation, shared). Framework locked to Next.js App Router for v1. Triggered by `/flow:retrofit-project` when `flow-preflight` mode classifier returns `retrofit`.