Flowguard

Overview

Use this skill as the single lifecycle entrypoint for agent work that can drift, lose context, or become expensive. It routes the task, verifies current state, runs bounded execution loops, and leaves a resumable handoff.

This skill coordinates other skills; it does not replace them. Use task-specific skills such as systematic-debugging, comprehensive-testing, codex-retrospective, or vibeguard only when their trigger is clearly met.

Operating Contract

• Do not start a long autonomous loop until route, scope, and stop conditions are explicit.
• Do not treat memory, summaries, or handoffs as current truth until repo, git, files, runtime, or remote state is verified.
• Do not claim completion without fresh verification evidence from the current session.
• Do not expand scope, touch destructive surfaces, or cross file-ownership lanes without stopping to re-route.
• Re-state the primary objective and a plan of no more than five steps before major phase changes.
• Prefer one controlling checkpoint over many specialized workflow fragments when the task risk is context loss, drift, or compounding errors.
• Before commit, push, PR, merge, or applying agent-generated changes outside the already-approved scope, call review-gate or produce the same review pack and wait for explicit human approval.

Route First