flow-run

Execute the complete FLOW workflow with checkpoints and quality gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Flow Run skill executes the full FLOW process across the repository, ensuring every step from BRANCH to ARCHIVE-REVIEW is completed with required checkpoints and quality gates.

Core Features & Use Cases

  • Orchestrates the end-to-end FLOW sequence: BRANCH, SELECT, PLAN, EXECUTE, ARCHIVE, REVIEW, FOLLOW-UP, ARCHIVE-REVIEW, PR, CI-REVIEW.
  • Enforces mandatory commit checkpoints via flow-primitive-commit and records artifacts in SPECS/INPROGRESS and SPECS/ARCHIVE.
  • Validates and enforces quality gates before merging or releasing code projects.

Quick Start

Start the full FLOW for the next task in this repository by starting with the BRANCH phase.

Frequently Asked Questions about flow-run

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

FAQPage Schema
How do I automate end-to-end task delivery for a software repository?

End-to-end task delivery is automated by orchestrating a complete workflow from BRANCH to ARCHIVE-REVIEW with mandatory commit checkpoints and quality gates. This coordinates all branching, planning, execution, review, and archival activities systematically.

What is a workflow orchestration process with mandatory commit checkpoints?

Workflow orchestration with mandatory commit checkpoints coordinates sequential phases like BRANCH, PLAN, EXECUTE, and REVIEW, enforcing quality gates before merging. It records artifacts in SPECS/INPROGRESS and SPECS/ARCHIVE to satisfy workflow definitions.

How do I enforce quality gates before merging code in a CI workflow?

Enforcing quality gates before merging code in a CI workflow requires validating and executing the complete sequence through CI-REVIEW and PR phases. This ensures all required checkpoints are satisfied before code is released or merged.

How do I manage in-progress and archived workflow artifacts?

Managing in-progress and archived workflow artifacts involves recording outputs under SPECS/INPROGRESS during execution and moving them to SPECS/ARCHIVE upon completion. This structure tracks task delivery status throughout the workflow lifecycle.

What's the best way to start an automated workflow for the next task in a repository?

Starting an automated workflow for the next task begins with the BRANCH phase. This initiates the full end-to-end sequence, coordinating all subsequent planning, execution, and review activities.

Does a FLOW workflow definition support pull request and continuous integration review?

A FLOW workflow definition supports pull request and continuous integration review through dedicated PR and CI-REVIEW phases. These phases validate quality gates and checkpoints before finalizing the end-to-end task delivery.