Loop Engineering Agent Skill
The engineering loop - select, advance, distill, deliver - for running a work session on a project. Invoke when STARTING a session or picking the next thing to work on; sizing a unit of work or matching it to your model tier; running long/autonomously and deciding pace or when to stop; deciding where a learning should live (lesson vs memory vs project-level skill); or wrapping up a unit/session (commit, report, handoff note).
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/telagod/code-abyss --skill loop-engineeringThe instruction itself
4 sections, as written by the authorLoop — the engineering cycle: select, advance, distill, deliver
Rule content lives in the four files below; this SKILL.md only routes
(doctrine/04-maintenance.md governs edits to this bundle too).
Route by moment
| You are about to… | Read (in this folder) |
|---|---|
| Start a session; choose the next unit; size it; decide who/which tier runs it | select.md |
| Push a unit forward; wonder if you're stalled; pace an unattended run | advance.md |
| Decide where a learning goes — lesson, memory, project-level skill, or nowhere | distill.md |
| Claim a unit done; commit; report; end the session | deliver.md |
A full pass is select.md → advance.md → distill.md → deliver.md, once per unit
of work; re-enter at select.md §5 after each landing.
Scope and neighbors
This bundle is the outer cycle that sequences the others across a session and a
project. *Whether/how to delegate and judge* (escalate, done-gate, ask-user) is
doctrine; *how to work a problem* once inside a unit (investigate, design, execute,
verify, write) is methods; domain judgment is the matching domain bundle. When this
bundle and doctrine both fire, doctrine first — its three non-negotiables apply
inside every phase of the loop.
The stance
**A project advances as a sequence of landed loops, and compounds only if each loop
distills.** Progress is landed deliverables, not activity (advance.md §3); the next
session's speed is this session's runway (deliver.md §4); and the institution grows
one filed learning at a time (distill.md §1) — that is how weak sessions get strong.
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take telagod/loop-engineering from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.