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.
• •Create a commit checkpoint after each major step using FLOW commit 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.

Step Procedure

1. •BRANCH

• •Ensure main is up to date.
• •Create feature/{TASK_ID}-{short-description} if not already on the correct feature branch.
• •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.
• •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.
• •Commit message pattern: Plan task {TASK_ID}: {TASK_NAME}.

1. •EXECUTE

• •Implement to the PRD.
• •Run quality gates defined in FLOW.
• •Create SPECS/INPROGRESS/{TASK_ID}_Validation_Report.md.
• •Commit message pattern: Implement {TASK_ID}: {brief description of changes}.
• •Split into incremental commits if the task is large.

1. •ARCHIVE

• •Run SPECS/COMMANDS/ARCHIVE.md workflow.
• •Verify task archive folder exists under SPECS/ARCHIVE/{TASK_ID}_{TASK_NAME}/.
• •Confirm SPECS/INPROGRESS/next.md and SPECS/Workplan.md are updated.
• •Commit message pattern: Archive task {TASK_ID}: {TASK_NAME} ({VERDICT}).

1. •REVIEW

• •Run SPECS/COMMANDS/REVIEW.md.
• •Save review report at SPECS/INPROGRESS/REVIEW_{subject}.md.
• •Commit message pattern: Review {TASK_ID}: {short subject}.

1. •FOLLOW-UP

• •If review has actionable findings, run SPECS/COMMANDS/PRIMITIVES/FOLLOW_UP.md.
• •Add follow-up tasks to SPECS/Workplan.md.
• •Commit message pattern: Follow-up {TASK_ID}: {short subject}.
• •If no actionable findings, explicitly note FOLLOW-UP skipped.

1. •ARCHIVE-REVIEW

• •Move REVIEW_{subject}.md to SPECS/ARCHIVE/_Historical/ or relevant task folder.
• •Update SPECS/ARCHIVE/INDEX.md.
• •Commit message pattern: Archive REVIEW_{subject} report.

Completion Criteria

Consider the run complete only when all are true:

• •FLOW step sequence has been fully executed (or optional FOLLOW-UP formally skipped due to no findings).
• •Required artifacts exist in SPECS/INPROGRESS/ and/or SPECS/ARCHIVE/.
• •Required quality gates were run and outcomes captured.
• •Commit checkpoints align with FLOW message patterns.

Trigger Phrases

Use this skill when requests look like:

• •"Do the next task from start to end."
• •"Run the full FLOW workflow for the next task."
• •"Take this task all the way through branch, plan, execute, archive, and review."
• •"Strictly follow the instructions in the @SPECS/COMMANDS/FLOW.md file carefully for the next task. Do not stop between steps. Complete each phase of the FLOW process one by one without asking questions or pausing."