plan-workflow SKILL.md skillA
plan-workflow from restarter/lets-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add restarter/lets-workflow/plan-workflow@git:20260915.64f0beePins git:20260915.64f0bee in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- restarter/lets-workflow
- Path
plugins/lets/skills/plan-workflow/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260915.64f0bee, committed Sep 15, 2026
- First version recorded
- Jun 5, 2026
- Size
- 9,009 bytes
- Repository stars
- 17
- License
- MIT
PREVIEW Dynamic Workflow asset behind /lets:plan-workflow. Not auto-triggered - a workflow script invoked via scriptPath. The autonomous-planning chain, shipped for cross-project testing before it folds into native /lets:plan.
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
# plan-workflow (PREVIEW Dynamic Workflow asset)
**Preview / experimental.** `plan.workflow.js` is the autonomous-planning chain, invoked by `/lets:plan-workflow` via:
```
Workflow({ scriptPath: "${CLAUDE_PLUGIN_ROOT}/skills/plan-workflow/plan.workflow.js", args })
```
It runs the autonomous design without touching the heavily-used interactive `/lets:plan`. Once stable (after cross-project testing), the asset folds into native `/lets:plan` (as a `--workflow` mode or equivalent) and this standalone is retired (lets-jsw00).
## Why this is autonomous-only (not a re-skin of review/opinion)
`/lets:review --workflow` and `/lets:opinion --workflow` are performance levers: same result, off-context. Native `/lets:plan` is interactive (clarify -> explore -> approaches -> architecture -> eval -> discuss); every checkpoint forces intermediate results back into context, which kills the off-context win. So the only workflow that pays off is the **autonomous whole-command** form: the user front-loads a RUBRIC, judge agents make the informed picks against it, and the run returns a plan + decision log. Steer-by-rubric + approve-at-end.
## Stages (off-context, NO user gate between them)
…Read the whole file at its exact version.
How to install
mdr add restarter/lets-workflow/plan-workflow@sha256:1c8dd792ddb002eeThe line at the top of this page pins the label git:20260915.64f0bee, 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_v6u5xoxmqd4tbav6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 5, 2026 and Sep 15, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260915.64f0bee latest | 2026-09-15 | 64f0bee | 9,009 B | A | view · diff |
| git:20260706.367aa8b | 2026-07-06 | 367aa8b | 7,648 B | A | view · diff |
| git:20260703.d1ae984 | 2026-07-03 | d1ae984 | 7,624 B | A | view · diff |
| git:20260611.0c699fa | 2026-06-11 | 0c699fa | 7,619 B | A | view · diff |
| git:20260605.68e8012 | 2026-06-05 | 68e8012 | 5,492 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 (9009 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
restarter/lets-workflow · 17 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v6u5xoxmqd4tbav6 GET https://markdownregistry.com/api/v1/resolve?ref=restarter/lets-workflow/plan-workflow GET https://markdownregistry.com/api/v1/blob/1c8dd792ddb002ee62f5a85af4a0de288f175606e0e7b6829663d510eb98327f
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.