flow-code

Enforce per-task tests, diffs, and CI gates in FLOW code phase workflows.

25|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/benkruger/flow --skill flow-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-code
Source: https://github.com/benkruger/flow/tree/main/skills/flow-code
Command: npx skills add https://github.com/benkruger/flow --skill flow-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 3 of FLOW orchestrates executing plan tasks one at a time with TDD, enforcing diffs review before each commit and requiring a passing CI gate before moving to the next task.

Core Features & Use Cases

  • Per-task TDD cycle with diffs reviews and targeted tests before commits.
  • CI-gated progression across tasks, with resume and atomic group handling for complex work.
  • Phase orchestration and logging to ensure traceability from code task to completion.

Quick Start

Run /flow:flow-code to begin executing Code-phase tasks with the selected mode and CI gating.

Frequently Asked Questions about flow-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a TDD workflow with CI gating for sequential code tasks?

Automate a TDD workflow with CI gating by enforcing per-task tests, diffs reviews, and CI gates before each commit. This ensures sequential code tasks progress only when CI passes, handling resume steps and atomic groups across multiple commits.

What is per-task TDD cycle enforcement in a multi-commit pipeline?

Per-task TDD cycle enforcement in a multi-commit pipeline mandates targeted tests and diffs reviews before every commit. It applies phase-enter mode resolution, strict code-task progression, logging, and finalization hooks to maintain traceability across complex work.

How do I handle resume steps and atomic groups across multiple commits in CI?

Handle resume steps and atomic groups across multiple commits by applying phase orchestration that enforces strict code-task progression. The workflow logs each step, ensuring CI-gated progression resumes accurately from the correct phase without losing traceability.

Does this code phase automation work without external dependencies?

Yes, this code phase automation works without external dependencies. It operates independently to enforce per-task TDD cycles, diffs reviews, and CI gating, relying solely on its internal phase orchestration and logging mechanisms.

Why do I need diffs review before each commit in a TDD workflow?

You need diffs review before each commit in a TDD workflow to enforce code quality and traceability. Reviewing diffs ensures the targeted tests validate the exact changes, preventing unreviewed code from passing the CI gate to the next sequential task.