loop-plan SKILL.md skillA
loop-plan from lploc94/cross-review is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lploc94/cross-review/loop-plan@git:20261019.e61debePins git:20261019.e61debe in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lploc94/cross-review
- Path
skill-packs/cross-review/skills/loop-plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.e61debe, committed Oct 19, 2026
- First version recorded
- Oct 15, 2026
- Size
- 9,100 bytes
- Repository stars
- 153
- License
- MIT
Create an execution-ready, code-grounded phased implementation plan before coding. Only for large work - several features, many files or components, or work spanning sessions that needs resumable phase boundaries. Not for small fixes or single-feature changes; do those directly.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Loop Plan
Create a plan that a fresh session, with only the repository and this file, can execute without guessing: nothing relies on this conversation, and each project-specific term is explained where first used. This skill plans only; it does not implement application code. Spikes live only under `.cross-review/spikes/<plan-name>/`.
Use it for large work: several features, many files or components, or work that spans sessions. For a small fix or a single-feature change, a phased plan and its reviews cost more time than they save: tell the user, and suggest doing it directly with tests (and `{{CLIENT_SKILL}}review-impl` if they want a review). Plan it only if the user still asks.
## Discovery and intent
1. Read applicable {{CLIENT_INSTRUCTIONS}}/repository instructions, inspect `git status`, recent history, relevant files, symbols, callers, commands, and existing tests before drafting.
2. Separate the user's target from reports, assumptions, completed work, and out-of-scope ideas. Preserve the user's expected behavior as the source of truth.
…Read the whole file at its exact version.
How to install
mdr add lploc94/cross-review/loop-plan@sha256:ee9cfc308cc2936cThe line at the top of this page pins the label git:20261019.e61debe, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wlm7eseieiu3b74h)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 15, 2026 and Oct 19, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.e61debe latest | 2026-10-19 | e61debe | 9,100 B | A | view · diff |
| git:20261016.4323b69 | 2026-10-16 | 4323b69 | 8,603 B | A | view · diff |
| git:20261016.2216115 | 2026-10-16 | 2216115 | 8,456 B | A | view · diff |
| git:20261015.082d695 | 2026-10-15 | 082d695 | 7,903 B | A | view · diff |
| git:20261015.61a3f61 | 2026-10-15 | 61a3f61 | 7,217 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9100 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lploc94/cross-review · 153 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wlm7eseieiu3b74h GET https://markdownregistry.com/api/v1/resolve?ref=lploc94/cross-review/loop-plan GET https://markdownregistry.com/api/v1/blob/ee9cfc308cc2936ca71793510afb908695b9e2f04857449db0f9d255ac8f36c0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.