Skip to content

feat(repo): flow-pack E5 — release gate (2nd-initiative dogfood + fresh-clone recovery + portability manifest) #375

@w7-mgfcode

Description

@w7-mgfcode

Sub-issue of #368 (umbrella: feat(repo): integrate flow-pack methodology as the flow: command suite). Release gate — closes only after Foundation (#369) + all Parallel epics (#371, #372, #373) close. All four are now CLOSED, so this gate is unblocked.

Purpose

Prove the flow: command suite works end-to-end on a second, independent initiative and is portable to a fresh checkout — the evidence that closes umbrella #368. E1–E4 delivered the four commands (/flow-prime, /flow-brainstorm, /flow-umbrella, /flow-epics) and the tracked contract; this epic validates that they actually run as a pipeline, that a fresh clone can regenerate the local install from tracked docs/flow-pack/, and that the portability manifest is accurate for reuse in another repo.

Scope

  • Second-initiative dogfood — drive a real (non-flow-pack) initiative through the full pipeline: /flow-prime/flow-brainstorm (V1→score→V2, 3 read-only subagents, .flow/ log) → /flow-umbrella (7-field body, approval-gated) → /flow-epics (phase-ordered epics + REST sub-issue links → prp-create handoff). Capture the resulting umbrella + epics as evidence.
  • Fresh-clone recovery — in a throwaway clone, run the documented recovery (mkdir -p .claude/commands/flow && cp docs/flow-pack/commands/*.md .claude/commands/flow/) and confirm all four commands install with zero drift (diff per file).
  • Portability manifest — verify the manifest in docs/flow-pack-methodology.md § Portability manifest: confirm the only repo-specific knobs are owner/repo, base_prp:prp-create, and core_piv_loop:prime; fix any drift.
  • Four-command install + run verification — confirm each of the four tracked templates under docs/flow-pack/commands/ parses and runs from a clean .claude/commands/flow/ install (no stale references; every gh invocation valid — e.g. the gh api .../milestones fix from feat(repo): flow-pack E2 — /flow-brainstorm (V1 → score → V2 + .flow logging) #371).
  • Umbrella close criteria — check off all 6 success criteria in feat(repo): integrate flow-pack methodology as the flow: command suite #368, then close it.

Out of scope

  • New flow: commands or command features (the suite is feature-complete at E4).
  • CI / git-hook enforcement of umbrella-issue.md (.claude/ is gitignored — out of scope per feat(repo): integrate flow-pack methodology as the flow: command suite #368).
  • Executing the second initiative's feature work — the dogfood stops at issue creation + prp-create handoff, the same boundary the suite itself observes.

Sub-tasks

  • Run the 2nd-initiative dogfood end-to-end; link the produced umbrella/epics as evidence
  • Fresh-clone recovery test — 4 commands install, diff clean
  • Verify + correct the portability manifest
  • Verify all 4 tracked templates run from a clean local install
  • Tick feat(repo): integrate flow-pack methodology as the flow: command suite #368's 6 success criteria and close the umbrella

Close criteria for umbrella #368

Umbrella #368 closes when, and only when:

  1. Tracked docs/flow-pack-methodology.md + 4 command templates committed — ✅ (verified at closeout)
  2. Local .claude/commands/flow/ install present — ✅
  3. Documented fresh-clone recovery reproduces the 4 commands — ⬜ (this epic)
  4. umbrella/epic/flow labels + a milestone exist — ✅
  5. A real umbrella+epics created by the suite appear under GraphQL subIssues — ✅ (feat(repo): integrate flow-pack methodology as the flow: command suite #368 itself: feat(repo): flow-pack E1 — foundation (/flow-prime + rule + tracked contract + labels/milestone) #369/feat(repo): flow-pack E2 — /flow-brainstorm (V1 → score → V2 + .flow logging) #371/feat(repo): flow-pack E3 — /flow-umbrella (7-field umbrella body, approval-gated write) #372/feat(repo): flow-pack E4 — /flow-epics (epic decomposition, sub-issue linking, prp-create handoff) #373); strengthened by the 2nd-initiative dogfood (this epic)
  6. /flow-brainstorm runs the 3-subagent V1→V2 loop and logs to .flow/ — ✅ (.flow/brainstorm-log.md); re-exercised by the dogfood

Durable-source split

  • No new tracked template (this epic is verification, not a new command).
  • Working artifacts: .flow/state.md, .flow/brainstorm-log.md, plus the 2nd-initiative's .flow/ logs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicEpic — a delivery surface under an umbrellaflowflow: command-suite work

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions