The readiness skill
The readiness skill helps you apply the framework to your team. It reads the current book, examines the evidence available in your project, and asks about how your team works. It proposes suitable loop sizes and identifies what limits further delegation. You might discover that a task needs closer supervision until its context or checks improve.
Point your agent at the repo
The skill lives in the project’s GitHub repository, in its own folder. Hand any capable agent that folder and ask it to install the skill it finds there. Your HarnessThe software around a model that lets it act, inspect results, and continue working: its execution loop, tools, context management, and controls. Harness engineering also covers checks and review arrangements across technical systems.An agent that can read files, run checks, and correct its work uses a harness. needs to support skills and retrieve the linked material.
Install this skill: https://github.com/youngbrioche/elastic-loop/tree/main/goodies/elastic-loop-readiness
A few prompts to get going
Ask for a diagnosis and say which work you know firsthand:
Run an elastic-loop readiness diagnosis with me. I am a product owner on a team that has started letting agents touch our codebase.
Or skip the self-report and let your own session history set the baseline:
Analyze my last 100 sessions in this project, take that as a starting point from an individual team member and start diagnosing our elastic loop readiness.
Or aim it straight at a question you already have:
We let agents do the work but never merge without reading every line. Where are our loop sizes a choice, and where are they an accident?
Or install it as a Claude Code plugin
If you are in Claude Code, there is a native path. Add the marketplace, install the plugin, reload:
/plugin marketplace add youngbrioche/elastic-loop
/plugin install elastic-loop-readiness@elastic-loop
/reload-plugins
Then ask for a loop-readiness diagnosis and Claude picks it up, or run it directly with /elastic-loop-readiness:elastic-loop-readiness. That is not a typo: the command reads plugin:skill, and here the plugin and the skill carry the same name.
Include people who see different aspects of the work, such as an engineer, a product owner, and a domain expert. Discuss where their assessments differ and what evidence would help resolve the disagreement. An individual diagnosis can give you a starting point, with the limits of that person’s view made explicit.
Check the skill’s conclusions against your experience and evidence from the project. The team remains responsible for deciding what to delegate.