flow-run

Flow Run

Execute the workflow in SPECS/COMMANDS/FLOW.md exactly, without skipping required steps unless the workflow itself explicitly allows skipping.

Required Inputs

Collect these before starting:

• Task identifier (for example P5-T2) and short description.
• Current branch and whether a feature branch already exists.
• Confirmation of which review subject name to use for REVIEW_{subject}.md.

If the task identifier is unknown, determine it from SPECS/Workplan.md and SPECS/INPROGRESS/next.md during SELECT.

Execution Contract

Apply these rules throughout execution:

• Read SPECS/COMMANDS/FLOW.md at the beginning and treat it as the source of truth.
• Complete steps in order: BRANCH -> SELECT -> PLAN -> EXECUTE -> ARCHIVE -> REVIEW -> FOLLOW-UP -> ARCHIVE-REVIEW -> PR -> CI-REVIEW.
• Use the flow-primitive-commit skill for every commit checkpoint — stage only task-relevant files and use present-tense FLOW message patterns.
• Run required quality gates during EXECUTE (pytest, ruff check src/, mypy src/ if configured, pytest --cov with coverage >= 90%).
• Record artifacts in expected locations under SPECS/INPROGRESS/ and SPECS/ARCHIVE/.
• If REVIEW has no actionable issues, skip FOLLOW-UP and proceed directly to ARCHIVE-REVIEW, as FLOW permits.
• After ARCHIVE-REVIEW, use the gh-create-pr skill to open a pull request from the feature branch into main.

Step Procedure

1. BRANCH

• Ensure main is up to date.
• Create feature/{TASK_ID}-{short-description} if not already on the correct feature branch.
• Use flow-primitive-commit skill — commit message pattern: Branch for {TASK_ID}: {short description}.

1. SELECT

• Choose the next task from SPECS/Workplan.md (optionally with python scripts/pick_next_task.py).
• Update SPECS/INPROGRESS/next.md with selected task metadata.
• Use flow-primitive-commit skill — commit message pattern: Select task {TASK_ID}: {TASK_NAME}.

1. PLAN

• Create the task PRD at SPECS/INPROGRESS/{TASK_ID}_{TASK_NAME}.md.
• Define deliverables, acceptance criteria, dependencies.
• Use flow-primitive-commit skill — commit message pattern: Plan task {TASK_ID}: {TASK_NAME}.