Skip to content
Skills Library
Programming · Building & coding

flow-execution

/flow-execution

Use when implementing Flow tasks from local task files under `.agents/bundles/specs/<flow_id>/tasks/`, claiming ready work, applying the declared verification strategy, recording task notes, committing, and updating task file state.

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
3
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 (3). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Use when implementing Flow tasks from local task files under `.agents/bundles/specs/<flow_id>/tasks/`, claiming ready work, applying the declared verification strategy, recording task notes, committing, and updating task file state.

Original author description

Use when implementing Flow tasks from local task files under `.agents/bundles/specs/<flow_id>/tasks/`, claiming ready work, applying the declared verification strategy, recording task notes, committing, and updating task file state.

How it works

  1. Trigger
  2. Workflow
  3. Guardrails
  4. Strategy Evidence
  5. Output
  6. Validation
  7. Example
Original SKILL.md headings · 67 lines, 414 words
SKILL.md preview
---
name: flow-execution
description: "Use when implementing Flow tasks from local task files under `.agents/bundles/specs/<flow_id>/tasks/`, claiming ready work, applying the declared verification strategy, recording task notes, committing, and updating task file state."
disable-model-invocation: true
---

# Flow Execution

<!-- lifecycle-ownership: owner=flow-execution; operations=implement -->

## Trigger

Use for `implement` only, after a validated plan contains ready task worksheets.

<!-- flow-execution-policy: start -->
```yaml
contract: worksheet-execution-v1
invariants:
  - worksheet-first
  - fail-closed-no-production-mutation
  - fresh-validated-plan-resume
transitions:
  - preflight-claim
  - mismatch-discover-block
  - nonblocking-discover-release
  - revised-plan-resume
authority: skills/flow/references/implement.md
```
<!-- flow-execution-policy: end -->

## Workflow

1. **Preflight**: Inspect `.agents/bundles/specs/<flow_id>/tasks/<short_id>.md`, verify dependencies are `closed`, and apply a journaled `claim` through `flow-state` with the expected plan identity and spec state revision.
2. **Initial Evidence**: Collect the declared strategy's required initial proof; only behavior and regression strategies require red.
3. **Minimal Implementation**: Make the smallest task-owned change while keeping focused evidence green.
4. **Quality Gates**: Run repository linters and typecheckers while tests remain green.
5. **Atomic Commit & Close**: Stage exact files, commit, apply a journaled `close` through `flow-state` recording `commit: <sha>`, and reconcile the `spec.md` checklist via `/flow:sync`.

## Guardrails

- Execute exactly one task per subagent dispatch.
- Never mark a task `closed` without running the test command and observing exit code 0.
- Stage only task-owned files; never perform opportunistic unrelated edits.
- Work on the active branch. Never create or mutate Git tags.

## Strategy Evidence

| Strategy | Initial evidence | Final evidence |
| --- | --- | --- |
| `behavior_tdd` | Focused behavior test fails because behavior is absent. | Focused test and relevant aggregate verification pass. |
| `regression_tdd` | Focused reproduction fails with the reported symptom. | Regression and relevant aggregate verification pass. |
| `characterization` | Focused behavior baseline passes before cleanup. | Same behavior passes unchanged; compare affected coverage when needed. |
| `static_validation` | Native parser, lint, type, build, or generator baseline runs. | Isolated representative violation produces the expected diagnostic; restored focused and aggregate gates pass. |
| `documentation_validation` | Documentation-native baseline runs. | Documentation checks and promised examples pass. |
| `integration_acceptance` | Focused integration baseline passes. | End-to-end scenario passes; injected negative states prove refusal paths. |

Do not manufacture a red result for characterization, static, documentation,
or integration work. Follow the full discipline and waiver rules in
[discipline.md](../flow/references/discipline.md).

## Output

Return the executed task ID, test command output, git commit SHA, and recorded discoveries.

## Validation

Confirm the test command produced exit code 0 and the commit SHA is recorded in task frontmatter.

## Example

For a task adding a route handler, write a failing endpoint test, implement the route to pass the test, commit locally, and close the task worksheet.
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

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

Database snapshot: 13.11.2026 · package version 772bb6009434 (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
    Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for building or planning work (use flow-next-flow).
  • 100flow-next
    Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).
  • 100take-task
    This skill should be used when claiming a task to work on - "take task", "візьми таск", "працюю над", "work on task X", "pick task X", "switch to task X", "claim task". Sets task to in_progress, creates/switches branch, saves the per-branch task-state file.
  • 100flow-planning
    Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/bundles/specs/<flow_id>/spec.md worksheets for Flow.
  • 100flow-setup
    Use when initializing Flow in a repo, configuring .agents, scaffolding OKF knowledge bundles, or creating first project context files.
  • 100execute
    Execute an approved implementation plan from .ai/plans/ task by task, running each task's verification and committing per task via the check-and-commit gate. Use when asked to "execute the plan", "implement the plan", or after /plan approval. Do not use without an approved plan…

Feedback and reports

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