claude-tweaks:flow

Orchestrate multi-step Claude Code pipelines with gate-driven progression and ledger tracking.

2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-tweaks:flow
Source: https://github.com/thomasholknielsen/claude-tweaks/tree/main/skills/flow
Command: npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flow automates end-to-end Claude Code lifecycles, running multi-step pipelines with gates to prevent proceeding on failures and ensure consistency.

Core Features & Use Cases

  • Orchestrates a full lifecycle (capture → challenge → brainstorm → specify → build → stories → test → review → wrap-up) in one command
  • Auto-inserts missing steps (e.g., test before review) and routes outputs through a central ledger
  • Supports design-mode, multi-spec pipelines, and worktree-based parallel runs for scalable team workflows

Quick Start

Invoke the full flow for a spec or design doc with /claude-tweaks:flow <spec-or-design-doc>.

Frequently Asked Questions about claude-tweaks:flow

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

FAQPage Schema
How do I automate a multi-step Claude Code pipeline with build and test gates?

Automate multi-step Claude Code pipelines by orchestrating gate-driven progression across build, test, review, and wrap-up stages. Flow ensures pipeline consistency by validating inputs and preventing progression on failures.

Can I run multiple specs sequentially in a single automated workflow?

Run multiple specs sequentially within a single automated workflow. Flow supports multi-spec sequencing and worktree-based parallel runs, routing all outputs through a central ledger for consistent tracking.

What is gate-driven progression in an automated coding lifecycle?

Gate-driven progression in an automated coding lifecycle validates each step's outcome before allowing the pipeline to proceed. Flow applies these gates to prevent proceeding on failures and auto-inserts missing steps like test before review.

How do I track story generation and lifecycle outputs across parallel worktrees?

Track story generation and lifecycle outputs across parallel worktrees by routing all pipeline outputs through a central ledger. Flow automatically creates this ledger and records gate outcomes for each run.

Does Flow support design-doc workflows or only spec-based projects?

Flow supports both spec-based projects and design-doc workflows. It orchestrates the full lifecycle from capture and brainstorm through specify, build, and wrap-up in a single command for either input format.

What happens if a required step like testing is missing from my pipeline?

If a required step like testing is missing from your pipeline, Flow auto-inserts it before the next dependent stage. This ensures complete lifecycle coverage without manual intervention.