flow-completion
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
Best use case
flow-completion is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
Teams using flow-completion should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/flow-completion/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How flow-completion Compares
| Feature / Agent | flow-completion | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Flow Completion Use this lifecycle skill for review, finish, archive, revert, docs, validation, and final cleanup work. ## Workflow 1. Run fresh verification before claiming a phase or flow is complete. 2. Review implementation against the spec, tests, patterns, security, architecture, and performance risks as appropriate. 3. Capture reusable learnings and elevate patterns into project knowledge. 4. Archive completed flows and preserve current-state guidance. 5. For reverts, identify the logical Flow scope and avoid unrelated user changes. ## Guardrails - No completion claim without fresh verification evidence. - Do not archive flows whose code, tests, Beads tasks, and markdown views disagree. - Do not revert unrelated files or user changes. - Keep knowledge chapters current-state oriented; avoid historical logs outside learnings. ## Validation - Run full relevant test and validation commands before finish/archive. - Confirm Beads tasks are closed or intentionally blocked/deferred. - Confirm `spec.md`, learnings, patterns, and knowledge chapters reflect the current state. ## References Index - [Review](../flow/references/review.md) - [Finish](../flow/references/finish.md) - [Archive](../flow/references/archive.md) - [Revert](../flow/references/revert.md) - [Docs](../flow/references/docs.md) - [Validate](../flow/references/validate.md) - [Cleanup](../flow/references/cleanup.md) ## Example User: "Finish this flow." Action: run verification, review against the spec, close or explain remaining tasks, sync markdown, elevate reusable patterns, and present finish options.
Related Skills
flow-memory-keeper
Use at task, phase, flow, sync, archive, finish, revise, or failure checkpoints to keep Flow specs clean, capture learnings and failures, elevate durable patterns, and refine this skill with project-specific nuances
flow
Use when a repository has .agents, when the user asks for Flow lifecycle routing, Beads-backed task memory, spec-first planning, TDD implementation, sync/status, review, finish, archive, or /flow:* help.
flow-sync-status
Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.
flow-setup
Use when initializing Flow in a repo, configuring .agents, installing or checking Beads bd, setting local-only sync policy, or creating first project context files.
flow-planning
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
flow-execution
Use when implementing Flow tasks from Beads or spec.md, claiming ready work, applying TDD, recording task notes, committing, and syncing after task state changes.
vue
Use when editing Vue projects, .vue files, vue.config.js, Vue 3 components, Composition API, <script setup>, SFC state, deployment workflows, or Vue CI configuration.
vite
Use when editing Vite projects, vite.config.ts, vite.config.js, Vite plugins, HMR, asset bundling, frontend build settings, deployment config, or Litestar/Vite integration.
uvicorn
Use when deploying ASGI apps with uvicorn, editing uvicorn CLI commands, Config or Server usage, workers, reload, event loop selection, SSL, lifespan, logging, or development server behavior.
tracer
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
testing
Use when writing or refactoring tests, editing test_*.py, *.test.ts, *.spec.ts, conftest.py, vitest.config.ts, pytest fixtures, mocks, coverage, async tests, anyio, or test failure debugging.
terraform
Use when creating, adopting, refactoring, or operating Terraform, *.tf files, .terraform.lock.hcl, terragrunt.hcl, root modules, backends, state, workspaces, imports, CI plan/apply, tests, or policy checks.