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
Development planning and architecture design.
## Routes
| Subcommand | Action |
| ---------- | ------ |
| `feature` | Plan a new feature |
| `refactor` | Plan refactoring |
| `architecture` | Architecture review |
## Usage
```bash
/plan # Ask what to plan
/plan feature # Plan a feature
/plan refactor # Plan refactoring
/plan architecture # Architecture review
```
## Behavior
All planning tasks use `EnterPlanMode` to create
a structured plan for user approval before any
implementation.
**After every plan is approved**, follow the
[Post-Plan Handoff](#post-plan-handoff) process.
### feature
Use `AskUserQuestion` to understand:
- What feature? What problem does it solve?
- What's the scope? Which files/modules?
- Any constraints or preferences?
Then use `EnterPlanMode` to design the implementation
plan. After approval, follow Post-Plan Handoff.
### refactor
Use `AskUserQuestion` to understand:
- What code needs refactoring?
- What's the goal? (simplify, split, extract)
- Any constraints?
Then use `EnterPlanMode` to plan the refactoring.
After approval, follow Post-Plan Handoff.
### architecture
…
The line at the top of this page pins the label v1.0.0, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_7uxqghzja4zz7rkq
GET https://markdownregistry.com/api/v1/resolve?ref=smart-ai-memory/attune-ai/plan
GET https://markdownregistry.com/api/v1/blob/2c46892bd8f9db77cd696464be5d8c5b46a95a0f2e3d88315cb0b270a6feae6d
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.
smart-ai-memory/attune-ai · .agents/skills/attune-hub/SKILL.md · Developer workflow hub — routes to the right skill based on what you need. Triggers on: attune, what can attune do…
smart-ai-memory/attune-ai · .agents/skills/author-feature/SKILL.md · Author a single-source feature page — a code-verified master that projects to .help kinds + docs pages, no API credits…
smart-ai-memory/attune-ai · .agents/skills/catalog/SKILL.md · Enumerate everything attune offers — every workflow, wizard, and tool, read live from the registries. Triggers on…
smart-ai-memory/attune-ai · .agents/skills/coach/SKILL.md · Progressive help for any topic. Repeat to go deeper: concept -> procedural -> reference. Triggers on: coach, learn…
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…
zereight/gitlab-mcp · .github/skills/plan/SKILL.md · Strategic planning with optional interview workflow. Activate when user says: plan this, plan the, let's plan, make a…
suboss87/fdeops · skills/plan/SKILL.md · Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use…
snowflake-labs/cocoplus · .cortex/skills/cocobrew/plan/SKILL.md · Enter the Plan phase of CocoBrew. Runs CocoSpec quality gate pre-flight, reads spec.md and discuss.md (if present)…
ericrisco/rsc-harness · skills/plan/SKILL.md · Use when an approved, clarified spec must become a technical blueprint before any code — the SDD phase between clarify…
aiskillstore/marketplace · skills/0xmsc/plan/SKILL.md · Guidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a…
