work-loop

Solid

Use 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.

Code & Development 21 stars 5 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
45
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Skill: work-loop ## Work-loop contract > **Surface** = stop the current loop, emit a brief description of the situation (what happened, what you tried, current state), name the minimum viable recovery rung, and wait for human direction. Do not retry, redispatch, or silently continue. Recovery rungs in cost order: **steer** (redirect this session with corrected instructions — cheapest; preserves context) / **rerun** (new session, gap-closed brief — keeps prior commits, discards context) / **salvage** (manual recovery from the last clean branch — use when agent state is irrecoverable). (Reviewers also "surface" findings in the descriptive sense — context disambiguates.) State flow: `PLAN → EXECUTE → GATES → REVIEW → DECIDE`. After a fix, return to GATES. ``` ┌─────────────────────────────────────────────────────────┐ │ │ ▼ │ PLAN ──► EXECUTE ──► GATES ──► REVIEW ──► DECIDE │ │ │ │ │ └─ failed? ─┴── findings? ──── fix ┘ └── back to GATES ``` **Self-coverage gate.** Between human gates, resolve everything a referent can resolve; surface only the irreducible. Three net-new obligations per loop: **(1)** conditional domain-grounding at PLAN (only when the build rests on an ungrounded domain claim); **(2)** resolve-v...

Details

Author
eugenelim
Repository
eugenelim/agent-ready-repo
Created
4 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