flow-linear-scaffoldlisted

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.
Brite-Nites/brite-claude-plugins · ★ 0 · AI & Automation · score 62

Install: claude install-skill Brite-Nites/brite-claude-plugins

# flow-linear-scaffold Per-domain Linear scaffolding sub-skill. Writes the foundational structure for every FDA domain: 1 milestone + N sub-flow parents + 5N discipline children + N Children-summary comments + a final milestone-description refresh. **2+7N writes per domain.** This skill is **NOT user-invocable** (`disable-model-invocation: true`, per Q7). Invoked from `/flow:start-project` (greenfield, per-domain), `/flow:retrofit-project` (retrofit, per-new-domain after `flow-legacy-cross-reference`), and `/flow:add-domain` (single-domain orchestrator). **Heaviest-mutation skill in the plugin.** All Linear writes go through `skills/_shared/linear-writeback-pattern.md` (Q46 layer). Preview-all -> one-approval -> execute -> log + pre-flight reads is the load-bearing pattern (cadence linear-housekeeping precedent). The full design rationale lives in `docs/design-rationale/fda-plugin-interview.md` Q13 (memory:80-93). Q22 (milestone schema), Q23 (parent-issue template), Q24 (discipline-child templates) are the upstream content contracts. --- ## 1. Mutation order (Q13.1) ### Per sub-flow execution unit ``` parent -> [Story] (foundation, no blockedBy) -> ([Design] || [Eng] in parallel, both blockedBy [Story]) -> [QA] (blockedBy [Eng] + [Design]) -> [Docs] (blockedBy [QA]) -> Children-summary comment on parent ``` **Execution graph:** `[Story] -> ([Design] || [Eng]) -> [QA] -> [Docs]`. Design and Eng parallelize AFTER Story exists --- NOT from the start. The `bloc