loop-planner SKILL.md skillA
loop-planner from ibrahim-3d/orchestrator-supaconductor is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ibrahim-3d/orchestrator-supaconductor/loop-planner@git:20260327.8972e9aPins git:20260327.8972e9a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ibrahim-3d/orchestrator-supaconductor
- Path
skills/loop-planner/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260327.8972e9a, committed Mar 27, 2026
- First version recorded
- Feb 17, 2026
- Size
- 9,416 bytes
- Repository stars
- 380
- License
- AGPL-3.0
Evaluate-Loop Step 1: PLAN. Use this agent when starting a new track or feature to create a detailed execution plan. Reads spec.md, loads project context, and produces a phased plan.md with specific tasks, acceptance criteria, and dependencies. Triggered by: 'plan feature', 'create plan', 'start track', '/conductor implement' (planning phase).
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 Planner Agent — Step 1: PLAN Creates detailed, scoped execution plans for tracks. This is Step 1 of the Evaluate-Loop. ## Inputs Required 1. Track `spec.md` — what needs to be built 2. `conductor/tracks.md` — what's already been done (to avoid overlap) 3. Track `plan.md` (if exists) — check for prior progress ## Workflow ### 1. Load Context read_file in order: 1. `conductor/tracks.md` — completed tracks and their deliverables 2. Track's `spec.md` — requirements for this track 3. Track's `plan.md` (if exists) — check what's already `[x]` done 4. `conductor/product.md` — product scope reference 5. `conductor/tech-stack.md` — technical constraints ### 2. Identify Scope Boundaries Before writing any plan: - List what `spec.md` asks for (deliverables) - List what's already done in other tracks (from `tracks.md`) - Identify overlap — anything in spec that was already delivered elsewhere - Flag overlap items as "SKIP — already done in [TRACK-ID]" ### 3. Create Phased Plan with DAG write_file `plan.md` with this structure (now includes dependency DAG for parallel execution): ```markdown # [Track Name] — Execution Plan ## Context - **Track**: [ID] …
Read the whole file at its exact version.
How to install
mdr add ibrahim-3d/orchestrator-supaconductor/loop-planner@sha256:2ad6d87f78fb913eThe line at the top of this page pins the label git:20260327.8972e9a, 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_fotyfuhepnxcky36)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Feb 17, 2026 and Mar 27, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260327.8972e9a latest | 2026-03-27 | 8972e9a | 9,416 B | A | view · diff |
| git:20260312.c37221c | 2026-03-12 | c37221c | 8,181 B | A | view · diff |
| git:20260217.9cad9a5 | 2026-02-17 | 9cad9a5 | 8,160 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 (9416 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
ibrahim-3d/orchestrator-supaconductor · 380 stars · license AGPL-3.0 · pushed 2026-09-27 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_fotyfuhepnxcky36 GET https://markdownregistry.com/api/v1/resolve?ref=ibrahim-3d/orchestrator-supaconductor/loop-planner GET https://markdownregistry.com/api/v1/blob/2ad6d87f78fb913e4f6e7b76fe397a32431db76dfbda837387c2169574821ff2
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.