feat(repo): integrate flow-pack methodology as the flow: command suite

[w7-mgfcode]

Summary

ForecastLabAI is rich at per-issue execution (PIV/PRP/do//validation) but has no front-door layer that turns a multi-step initiative into a GitHub umbrella -> epics. Issues are flat, unlabeled, and there are no milestones. This umbrella lands a reusable flow: command suite that reverse-engineers the "continuation -> decomposition" methodology and wires it into .claude + GitHub.

Approach

Four thin, reusable slash-commands that delegate to existing primitives (core_piv_loop:prime, 3 read-only subagents, gh api, base_prp:prp-create) — no agent-teams, no new runtime deps. The durable contract AND the command templates live in tracked docs/flow-pack/ (methodology.md + commands/); .claude/commands/flow/ is a local runtime install regenerable from those templates (.claude/ is gitignored, so it is never the durable artifact).

Decomposition

• E1 — Foundation (blocks E2–E5): /flow-prime + umbrella-issue.md rule + docs/flow-pack-methodology.md + docs/flow-pack/commands/ tracked templates + fresh-clone recovery + labels/milestone. (linked as a sub-issue)
• E2 — Parallel: /flow-brainstorm (V1->V2, 3 read-only subagents, .flow/ logging) — not yet created
• E3 — Parallel: /flow-umbrella (rule-driven umbrella gen via gh api) — not yet created
• E4 — Parallel: /flow-epics (epic decomposition + create-then-link, hand to prp-create) — not yet created
• E5 — Release gate: end-to-end dogfood on a 2nd initiative + finalize docs + portability manifest — not yet created

Out of scope (explicit)

• /flow-analyze as a standalone command — overlaps analyzing-ai-repos; folded into /flow-prime//flow-brainstorm; revisit only if a future initiative needs deep external reverse-engineering.
• /flow-execute — the suite stops at issue creation; execution is owned by base_prp:prp-create / core_piv_loop:execute.
• Agent-teams/tmux orchestration — research fan-out is read-only subagents; no coordination needed.
• CI/git-hook enforcement of the rule — .claude/ is gitignored; the enforceable narrative lives in tracked docs/.

Success criteria

• Tracked docs/flow-pack-methodology.md + docs/flow-pack/commands/{flow-prime,flow-brainstorm,flow-umbrella,flow-epics}.md committed — the canonical templates/spec.
• Local .claude/commands/flow/ install present (regenerated from the tracked templates) — explicitly not the committed durable artifact.
• Documented fresh-clone recovery reproduces the local commands from tracked docs.
• umbrella/epic/flow labels + one milestone exist.
• A real umbrella+epics created by the suite appear under GraphQL subIssues.
• /flow-brainstorm runs the 3-subagent V1->V2 loop and logs to .flow/.

Risks

Risk	Mitigation
.claude/ gitignored -> rule/commands lost on fresh clone	Durable contract AND command templates committed to tracked docs/flow-pack/; .claude/ holds only a regenerable install
Accidental/duplicate gh issue writes	Dry-run echo + idempotent title check + approval-gated writes
/flow-epics overlaps issue-to-subtasks	Scope carve: epics != subtasks; subtasks delegated downstream
Sub-issue API / rate limits	gh api create-then-link + rate-delay; API confirmed available

Tracking

• Project: KnowRAG Full UI (PVT_kwHOCghNdc4BXSuW) or a new "Flow Pack" project (later call).
• Source of truth: docs/flow-pack-methodology.md + KB sources (ai_engineering_mermaid_flow_pack/docs/flow-analysis/*).
• Working artifacts: .flow/state.md, .flow/brainstorm-log.md.
• One-pass confidence: 8/10 (deps confirmed, methodology dogfooded; -2 for first-time gh api sub-issue writes + the gitignore split).

[w7-mgfcode]

Progress update — E4 closed, all commands shipped

Epic	Issue	Status	Delivered
E1 Foundation	#369	✅ CLOSED	/flow-prime + rule + methodology doc
E2 Parallel	#371	🟡 OPEN	/flow-brainstorm — command on dev (d023a20)
E3 Parallel	#372	🟡 OPEN	/flow-umbrella — command on dev (9679ce8)
E4 Parallel	#373	✅ CLOSED	/flow-epics — command on dev (ae1c201, PR #374)
E5 Release gate	—	⏭️ deferred	end-to-end dogfood + portability manifest

All 4 command files are tracked under docs/flow-pack/commands/ and regenerable locally via cp docs/flow-pack/commands/*.md .claude/commands/flow/. Sub-issues E2/E3/E4 are linked under this umbrella (verified via GraphQL). E5 closes this umbrella once E2 and E3 epics close.