Plan mode: write markdown plan to .mateclaw/plans/, no exec.
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 Mode
Use this skill when the user wants a plan instead of execution.
## Core behavior
For this turn, you are planning only.
- Do not implement code.
- Do not edit project files except the plan markdown file.
- Do not run mutating terminal commands, commit, push, or perform external actions.
- You may inspect the repo or other context with read-only commands/tools when needed.
- Your deliverable is a markdown plan saved inside the active workspace under `.mateclaw/plans/`.
## Output requirements
Write a markdown plan that is concrete and actionable.
Include, when relevant:
- Goal
- Current context / assumptions
- Proposed approach
- Step-by-step plan
- Files likely to change
- Tests / validation
- Risks, tradeoffs, and open questions
If the task is code-related, include exact file paths, likely test targets, and verification steps.
## Save location
Save the plan with `write_file` under:
- `.mateclaw/plans/YYYY-MM-DD_HHMMSS-<slug>.md`
Treat that as relative to the active working directory / backend workspace. the agent file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.
…
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_ctmrsamk4c75z63k
GET https://markdownregistry.com/api/v1/resolve?ref=mateaix/mateclaw/plan
GET https://markdownregistry.com/api/v1/blob/1227de43cb02fa640735bf5ebbf79989f00f09cbba162a93095a554dc3132452
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.
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)…
aiskillstore/marketplace · skills/0xmsc/plan/SKILL.md · Guidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a…
boshu2/agentops · skills/plan/SKILL.md · Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use…
boshu2/agentops · plugin/skills/plan/SKILL.md · Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use…
