Skip to content
Skills Library
Programming · Review & audit

flow-completion

/flow-completion

Use when reviewing, finishing, archiving, reverting, validating, documenting, or cleaning up Flow work after implementation or phase completion.

Author
cofin ↗
Repository
flow ↗
Licence
Apache-2.0
Last repository change
26.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
5
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • SKILL.md zawiera komentarze HTML (5). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Use when reviewing, finishing, archiving, reverting, validating, documenting, or cleaning up Flow work after implementation or phase completion.

Original author description

Use when reviewing, finishing, archiving, reverting, validating, documenting, or cleaning up Flow work after implementation or phase completion.

How it works

  1. Trigger
  2. Workflow
  3. Guardrails
  4. Output
  5. Validation
  6. Example
  7. Custom Completion Checks
Original SKILL.md headings · 50 lines, 259 words
SKILL.md preview
---
name: flow-completion
description: "Use when reviewing, finishing, archiving, reverting, validating, documenting, or cleaning up Flow work after implementation or phase completion."
disable-model-invocation: true
---

# Flow Completion

<!-- lifecycle-ownership: owner=flow-completion; operations=review,finish,archive,revert,docs,cleanup,validate,resynthesize -->

## Trigger

Use for `review|finish|archive|revert|docs|cleanup|validate|resynthesize`.

<!-- 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, archive]
runtime_dependency: agent_file_tools_only
evaluator_module: forbidden
```
<!-- quality-completion-policy: end -->

## Workflow

1. **Two-Axis Review (`/flow:review`)**: Run parallel reviewers evaluating Standards/Smells (Security, Performance, Debloat lenses) and Spec Conformance against `git diff <base>...HEAD`.
2. **Finish Flow (`/flow:finish`)**: Run full test verification suite and record single-paragraph ADRs in `knowledge/decisions/`.
3. **Archive Flow (`/flow:archive`)**: Synthesize discoveries into project-shaped knowledge, append one `log.md` entry, and delete the reviewed completed spec inventory through a journaled archive operation.
4. **Resynthesize Knowledge (`/flow:resynthesize`)**: Audit and rewrite `.agents/bundles/knowledge/` in depth against current codebase truth, reorganizing flat or bloated chapters into hierarchical OKF v0.2 subdirectories and rebuilding `index.md`.
5. **Cleanup, Revert, or Validate (`/flow:cleanup`, `/flow:revert`, `/flow:validate`)**: Sweep completed flows and code/prose bloat in touched files, revert designated changes, or run repository validation checks.

## Guardrails

- Reviews are read-only; report concrete evidence with file/symbol references.
- Archive leaves a terminal journal outside the bundle and no resident archived spec.
- Preserve Git history. Never create or mutate Git tags.

## Output

Return the review assessment, verification evidence, ADR summaries, or archived flow manifest.

## Validation

Confirm test suites pass cleanly, no blocking review findings remain, and knowledge synthesis is complete.

## Example

For flow completion, run tests, review the diff against `main`, elevate reusable patterns to evidence-backed `knowledge/patterns/<topic>.md` chapters, and archive the spec directory.

<!-- project-customization: start -->
## Custom Completion Checks
<!-- project-customization: end -->
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · cofin/flow100Apache-2.0
cofin/flow100Apache-2.0
cofin/flow100Apache-2.0

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 1ae603bc4ef7 (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

  • 100flow-next-spec-completion-review
    Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
  • 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
  • 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
  • 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.
  • 100finishing-work
    Structured completion workflow for implementation work. Use when implementation is complete, all tests pass, and you need to decide how to integrate the work. Guides merge, PR creation, or cleanup decisions.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.