work-loop
SolidUse when implementing or resuming a non-trivial repository change: a feature, behavior-changing fix, refactor, migration, framework or dependency upgrade, schema or API change, performance work, infrastructure or build-system change, reversion, or an existing build spec under `docs/specs/`. Also use for bare continuation commands ('resume', 'continue', 'keep going', 'pick up where I left off', 'let's get going') when conversation or workspace context identifies active build work. Do not use for shaping, research, strategy, product planning, design exploration, monitoring or status-only work, review-only, explanation-only, specification-authoring-only, spike-only or throwaway exploration, or trivial edits that are cosmetic, tightly local, behavior-preserving, and have obvious verification.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- eugenelim
- Repository
- eugenelim/agent-ready-repo
- Created
- 3 months ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
loop-engineering
Use when designing, running, or resuming a loop, or mapping the five moves to repo mechanics. Covers discovery, handoff via worktrees, verification, persistence, and scheduling, plus grep-countable stop conditions, deterministic tripwires, and the git-trust and cycle-count resume rules.
implementation-loop
Delegate implementation to Codex, grok, or cursor-agent, then review the diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex, the grok 后端, or cursor-agent to write code, mentions handing off / delegating implementation to one of those backends, asks to work through a plan or spec unit-by-unit with an implementation backend doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer runs in the real environment behind backend-specific git and publication boundaries, must not be pointed at a full test suite by default, and its self-report is a claim rather than evidence. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the engineering-mode skill when it is installed.
loop-engineering
Loop-mode discipline for orchestrated runs — recognize loop intent ("keep going until done", "loop this", "finish it", "clear all the stale ones", "bump everything SAFE"), offer to loop on open-ended work, and run to completion under explicit stop rules that always end at the run's terminal gate. Preload into orchestrator agents (crew's morpheus, keymaker); each defines its own bindings. Use whenever the user asks to keep going, loop, or finish the work without further check-ins.