flow-journey-authorlisted

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 — programmatic substitution for 8 deterministic top-level YAML keys + 2 body items; single `Agent(general-purpose)` 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. 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 finish in ~90s, N=27 finishes in ~270s (3 batches under the cap).
Brite-Nites/brite-claude-plugins · ★ 0 · Data & Documents · score 64

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

# flow-journey-author Per-domain journey doc authoring sub-skill. Writes ONE markdown file per domain conforming to the Q26 locked journey-doc template. Single `Agent(general-purpose)` per domain --- multi-agent staged authoring is parked for v1.1 if domain content bloats past context limits. This skill is **NOT user-invocable** (`disable-model-invocation: true`, per Q7). **Ordering constraint.** Runs AFTER `flow-doc-author` (Q15). Even greenfield `NOT_STARTED` stubs confirm flow IDs + personas + related_flows for journey authoring. Uniform ordering simplifies the orchestrator --- the ~60s parallelism savings on greenfield doesn't justify conditional ordering against ~5min/gate human review time on retrofit. The full design rationale lives in `docs/design-rationale/fda-plugin-interview.md` Q16 (memory:126-145). Q26 defines the journey-doc template; Q15 (memory:108-124) defines the upstream story-doc author this skill reads from. --- ## 1. Authoring strategy (Q16.1) --- hybrid ### Programmatic substitution (8 deterministic YAML keys + 2 body items) | YAML key | Source | |---|---| | `domain` | inventory section | | `milestone` | scaffold output (`BC-XXXX`) | | `personas` | deduplicated from inventory rows OR `personas/INDEX.md` | | `flow_ids_in_scope` | inventory domain section row IDs | | `status` | `in-progress` initial (describes doc-authoring lifecycle, NOT delivery state) | | `figma` | `TBD` | | `last_reviewed` | current ISO-8601 | | `intent` | `../intent.md` (per