From flow
> **Trigger**: User wants to kill, merge, or archive a cycle. "Kill this", "we're done", "ship it", "close this out".
How this skill is triggered — by the user, by Claude, or both
Slash command
/flow:flow-closeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Trigger**: User wants to kill, merge, or archive a cycle. "Kill this", "we're done", "ship it", "close this out".
Trigger: User wants to kill, merge, or archive a cycle. "Kill this", "we're done", "ship it", "close this out". Routes to G3 Resolve if not already done, then handles archival.
Read .flow/cycles/ for active cycles.
If user names a specific cycle: Use that one.
If one active cycle: Use that one.
If multiple: List and ask which to close.
If no active cycles: "No active cycles to close. Did you mean to start one with /flow-start?"
Has this cycle already been through G3 Resolve?
If no G3 record exists: "This cycle hasn't been through G3 Resolve yet. Let's do that now." -> Run the G3 Resolve flow from /flow-check Step 4.
If G3 already completed: Proceed to archival.
Before archiving, check if a Learning Entry exists for this cycle.
If no Learning Entry: Do NOT proceed to archival. Ask:
"Every cycle teaches something — even a 'this worked as expected' is a learning. What did you learn?"
Prompt with:
Write the Learning Entry to .flow/cycles/[slug]-learning.md:
# Learning Entry
Date: [today]
Cycle: [link to brief]
What we tested: [one sentence]
What we learned: [2-3 sentences]
What this means: [future implications]
If Learning Entry exists: Proceed.
.flow/archive/.flow/cycles/ (remove from active)After closing, offer forward momentum:
/flow-start something?"/flow-check it?"Respectful of the closure moment. Killing work is hard — acknowledge the learning, not just the stop. "That cycle produced a Learning Entry that will save future work. Good kill."
npx claudepluginhub onestudio-os/flow-skills --plugin flowFinalizes task or workflow closeout after completion gate approval by syncing state, generating release notes/changelogs, and creating handoff packs.
Reviews, finishes, archives, reverts, validates, and cleans up Flow work after implementation phases, with verification, spec checks, test runs, and knowledge capture.
Manages Hypo-Workflow Cycles with independent milestone sequences, state, progress, reports, archives, and summaries. Supports creating, listing, viewing, and closing cycles with type/preset mapping and context sources.