plan is agent-read markdown (skill) from swingerman/engineer: Use when a feature has ACs and specs and needs an architecture plan before implementation. Triggers — "/engineer.plan", "plan this feature", "plan the implementation", "design the architecture"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# plan
Produce a feature's architecture plan — Checkpoint 4, the most consequential architectural checkpoint. Where engineering authority over **code design** and **performance** is exercised: the agent proposes, the human decides.
Mixed mode — the agent proposes the architecture, the human confirms it, then the rest of the plan is drafted.
## When to use
After `discover-acs` (Checkpoint 2) and `atdd:atdd` (Checkpoint 3). Produces `plan.md`.
If `spec.md` is missing, warn — planning should follow spec formalization — but the user may override and plan from `acs.md` alone (flag the skipped step in the handoff).
**Not for:** Given/When/Then specs (`atdd:atdd`); small changes to an existing plan (`feature-edit`).
## Workflow
**Step 0 — Entry gate.** Before starting, verify the prior checkpoint is complete: run `${CLAUDE_PLUGIN_ROOT}/scripts/dae_handoff.py <feature-dir> --through 3`. On a non-zero exit, **stop** and surface the gap to the human — do not proceed.
Verify branch hygiene: run `${CLAUDE_PLUGIN_ROOT}/scripts/dae_branch.py <feature-dir>`.
On a non-zero exit, **stop** and surface the message to the human — switch
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_ihugjbnqie2pjsy7
GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/plan
GET https://markdownregistry.com/api/v1/blob/e8d15c2605d14ccb17a489bf3a330fef0f4132d0683ac1bfbb19bbc0fe07fe41
Your agent 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.
swingerman/engineer · crap-analyzer/skills/crap-analyzer/SKILL.md · Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP…
swingerman/engineer · engineer/skills/arch-check/SKILL.md · Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden…
swingerman/engineer · engineer/skills/atdd/SKILL.md · Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. The…
swingerman/engineer · engineer/skills/clarify/SKILL.md · Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec"…
swingerman/engineer · engineer/skills/consistency-check/SKILL.md · Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers —…
swingerman/engineer · engineer/skills/discover-acs/SKILL.md · Use when a Ready feature needs its acceptance criteria discovered before specs are written. Triggers —…
swingerman/engineer · engineer/skills/discuss/SKILL.md · Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss"…
swingerman/engineer · engineer/skills/express/SKILL.md · Use to build an XS (express-lane) feature in one pass — intake→implement→verify in a single context, no handoff chain…
swingerman/engineer · engineer/skills/feature-edit/SKILL.md · Use when an in-flight feature must change — scope shifts, an AC is refined, the plan evolves, a behavior is added or…
swingerman/engineer · engineer/skills/feature-init/SKILL.md · Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers —…
swingerman/engineer · engineer/skills/fix/SKILL.md · Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers —…
swingerman/engineer · engineer/skills/next/SKILL.md · Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project…
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/plan/SKILL.md · Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to…
suboss87/fdeops · skills/plan/SKILL.md · Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use…
greenfield-inc/pane · .codex/skills/plan/SKILL.md · Creates a reconciled implementation plan by combining a structured plan draft with a normalized intent brief and a…
dcouple/pane · .codex/skills/plan/SKILL.md · Create a detailed implementation plan for a feature or significant change, grounded in codebase research and external…
