flow-completion
/flow-completion
Use when reviewing (/flow:review), finishing (/flow:finish), archiving (/flow:archive), cleaning up (/flow:cleanup), reverting (/flow:revert), or validating (/flow:validate) Flow work.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 3
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- SKILL.md zawiera komentarze HTML (3). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Use when reviewing (/flow:review), finishing (/flow:finish), archiving (/flow:archive), cleaning up (/flow:cleanup), reverting (/flow:revert), or validating (/flow:validate) Flow work.
Original author description
Use when reviewing (/flow:review), finishing (/flow:finish), archiving (/flow:archive), cleaning up (/flow:cleanup), reverting (/flow:revert), or validating (/flow:validate) Flow work.
How it works
- Trigger
- Workflow
- Guardrails
- Output
- Validation
SKILL.md preview
---
name: flow-completion
description: "Use when reviewing (/flow:review), finishing (/flow:finish), archiving (/flow:archive), cleaning up (/flow:cleanup), reverting (/flow:revert), or validating (/flow:validate) Flow work."
disable-model-invocation: true
---
# Flow Completion
<!-- lifecycle-ownership: owner=flow-completion; operations=review,finish,archive,cleanup,revert,validate -->
## Trigger
Use for `review` ([`../flow/references/review.md`](../flow/references/review.md)), `finish` ([`../flow/references/finish.md`](../flow/references/finish.md)), `archive` ([`../flow/references/archive.md`](../flow/references/archive.md)), `cleanup` ([`../flow/references/cleanup.md`](../flow/references/cleanup.md)), `revert` ([`../flow/references/revert.md`](../flow/references/revert.md)), and `validate` ([`../flow/references/validate.md`](../flow/references/validate.md)).
<!-- quality-completion-policy: start -->
```yaml
contract: quality-completion-v1
authority: skills/flow/references/review.md
finish_gates: [verification, code_review, quality_review, finish]
archive_gates: [archive_candidate, verification, code_review, quality_review, knowledge_contraction, archive]
runtime_dependency: agent_file_tools_only
```
<!-- quality-completion-policy: end -->
## Workflow
1. **Zero-Context Chapter or Flow Correctness, Markdown-Sync, & Quality Review (`/flow:review [flow_id] [chapter_id]`)**:
- Compute the exact `base_commit..head_commit` range for the target chapter or full flow and inspect the changed code, test, spec, OKF, and doc surface.
- Dispatch isolated zero-context reviewers (`run_workflow(ScriptPath="<plugin_root>/workflows/flow-dual-review/workflow.py", Args={...})` with `type_name="self"` on Google Antigravity, checking `git status --porcelain` afterward; isolated `@code-reviewer`, `@quality-reviewer`, and matching `.agents/agents/<domain>-reviewer` subagents elsewhere; `review_mode: "single"` for `Small` single-chapter `<= 2`-task flows, `"dual"` otherwise, using **Opus** on Claude Code when available [else `sonnet`] and **Gemini Pro** / Pro-Next on Antigravity when available [else `flash` on quota fallback]—**never** `flash_lite` / `haiku`) passing only disk paths (`spec.md`, `chapters/index.md`, `chapters/<ch_id>/spec.md`, `tasks/*.md`, `.agents/skills/`, and `knowledge/` chapters) under the **Zero-Context Isolation Rules**.
- Evaluate **Spec Conformance**, **Present-Tense Markdown, Full-Plan Roadmap, & Doc-Sync Conformance**, **Repository Standards, Deep-Module Seams, & Baseline Structural Code Smells**, and **Mandatory Quality, Zero-History Doc Hygiene, & Debloat Review (`quality-review-v1`)**.
- Adjudicate findings (`ADOPT` vs. `CONTEST` vs. `ESCALATE`), remediate adopted code or Markdown-drift findings, re-verify, and stamp `last_reviewed_commit: <REVIEWED_HEAD_SHA>` on the reviewed chapter/flow `spec.md`.
2. **Finish Flow (`/flow:finish`)**:
- Run the deterministic anti-skip and OKF completion audit (`/flow:validate` on `<flow_id>`): verify zero chapters or tasks remain `planned`/`pending`/`open`/`in_progress`/`blocked`, every `deferred` item carries `deferred_by: "user"` and non-empty `deferred_reason`, every completed task commit SHA modified at least one declared path in `files:` or `tests:`, every completed chapter carries a valid hex `last_reviewed_commit` covering all chapter task commits, and `[N/N files documented]` is satisfied in `## 3. Documentation & OKF Knowledge Plan`. If `planning_quality: degraded` is present on `spec.md`, remind the user before final sign-off.
- Run the **Full Release Gate** (`knowledge/workflow.md`, including any `> 60s` full test suite deferred during fast chapter gates), confirm flow-wide review gates passed, evaluate the **ADR Filter** (`knowledge/decisions/adr-NNN-<slug>.md`), mark root `spec.md` `state: completed` (`current_chapter: null`, `current_task: null`), and present the structured completion options (`Archive flow now`, `Archive and open/update PR`, `Merge locally and archive`, `Discard work`).
3. **Archive & Contract Flow (`/flow:archive`)**:
- Verify `/flow:validate` passes completion and anti-skip checks on `<flow_id>` (`state: completed` with zero open chapters/tasks) before touching `specs/<flow_id>/`. In linked `local-only` Git worktrees, apply `.agents/` contraction directly to the primary checkout's `.agents/` bundle.
- Execute the subagent-sharded `/flow:learn` contraction pass (`1` subagent per domain when `>= 2` domains) across all chapters, OKF knowledge namespaces, and `.agents/skills/**` before deletion.
- Enforce strict write ordering: write `knowledge/**` + `.agents/skills/**` first, prepend the `archive` entry to `.agents/bundles/log.md` second, delete `.agents/bundles/specs/<flow_id>/` (including `chapters/`) last, and run `/flow:validate` afterward to confirm zero broken links.
4. **Cleanup, Revert, or Validate (`/flow:cleanup`, `/flow:revert`, `/flow:validate`)**:
- Run groundskeeping and `debloat` across touched files (`/flow:cleanup`), revert designated `task`, `chapter`, `phase`, or `flow` commits while resetting chapter/root roadmaps in present tense (`/flow:revert`), or run the deterministic OKF v0.2 bundle, workflow AST, schema-card, anti-skip, worktree, hook, skill, and spec validator (`/flow:validate`).
## Guardrails
- Reviewers are strictly read-only isolated agents and receive zero conversational history, rationale, or leading hints.
- Never stamp `last_reviewed_commit` or close a chapter/flow until both code/tests AND present-tense Markdown/OKF/user docs (`spec.md`, `chapters/index.md`, `knowledge/**`, `docs/**`) are synchronized and verified free of historical prose.
- Never delete a completed spec directory during `/flow:archive` until its durable discoveries and patterns across all chapters have been synthesized into `.agents/bundles/knowledge/**` and logged in `.agents/bundles/log.md`.
- Preserve Git history and never create or mutate Git tags.
## Output
Return the review adjudication summary (`ADOPT` / `CONTEST` / `ESCALATE`), verification command exit codes, updated `spec.md` state or `.agents/bundles/knowledge/` contraction report, and next action.
## Validation
Confirm all required review and verification gates passed with exit code `0`, `spec.md` and `tasks/*.md` states match Git history, and `.agents/bundles/index.md` and `log.md` are updated cleanly.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · cofin/flow | 100 | Apache-2.0 |
| cofin/flow | 100 | Apache-2.0 |
| cofin/flow | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version cb1c159ec7b6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90flow
Use when a repository has .agents, when the user asks for Flow lifecycle routing, OKF v0.2 bundle task tracking, spec-driven planning, TDD implementation, status, learn/resynthesize, review, finish, archive, or /flow:* help. - 100flow-next-spec-completion-review
Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review. - 100flow
Use when a repository has .agents, when the user asks for Flow lifecycle routing, OKF bundle task tracking, spec-first planning, TDD implementation, sync/status, review, finish, archive, or /flow:* help. - 100finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup - 100finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup - 100finish
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup