loop-workflow-planner

Loop Workflow Planner

Purpose

Create a platform-neutral Loop Workflow Contract for standard or deep work that must iterate until measurable acceptance criteria pass.

This skill does not implement code. It defines objective, scope, verification, retry limits, stop conditions, independent review, and memory update rules so Codex, GPT-based agents, Claude, and generic coding agents can execute the same workflow without depending on Claude-only commands.

When To Use

Use this skill when the task is Standard Workflow or Deep Workflow and one or more are true:

• the user asks to continue until lint, typecheck, build, visual QA, CI, or another measurable check passes;
• verification may fail and repair is in scope;
• a repeated failure already happened;
• a bugfix, CI repair, refactor, or UI implementation needs bounded retry;
• independent review should judge completion;
• the work may need resumable memory;
• multiple agents or worktrees are being considered.

When Not To Use

Do not use for:

• Fast Lookup;
• one obvious typo or type error;
• tiny direct edits;
• pure explanation;
• design-only direction with no iterative verification;
• platform-specific /goal, /loop, or /schedule commands without a platform-neutral contract;
• unbounded autonomous work.

Required Context

1. Read AGENTS.md.
2. Read common/agent-loop-policy.md.
3. Read common/stop-criteria-rules.md.
4. Read common/bounded-retry-rules.md.
5. Read common/verification-loop-rules.md.
6. Read common/context-compaction-rules.md when stop/resume or memory matters.
7. Read common/independent-review-rules.md when review is needed.
8. Read common/worktree-parallelism-rules.md only when parallel agents, branches, or worktrees are considered.
9. Read the current Goal Contract, Execution Plan, user request, or project/active-goals.md when present.
10. Read the active coverage map and target S-### slices when a durable plan exists.
11. Read project/verification-profile.md when verification commands matter.