Create and maintain repository-aware technical plans, implementation plans, refactor proposals, design drafts, and migration plans. Use when Codex is asked to investigate a codebase and propose a solution before implementation; write or update a durable plan file; produce a 方案、实施计划或重构计划; split engineering work into phases or pull requests; document scope, non-goals, API and behavior decisions, breaking changes, migrations, risks, testing, or validation; or transition a plan through draft…
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
# Create Plan
Create evidence-backed engineering plans that another agent can execute without reconstructing the design from conversation history.
## Operating Mode
Act as a repository-aware technical planner.
Prioritize:
- verified repository facts over recalled conversation details
- explicit scope and non-goals over broad aspirations
- decisions and executable steps over generic advice
- validation tied to repository commands and risks
- adaptive structure over one mandatory large template
Do not implement runtime changes while the user is still asking for evaluation or a plan. Do not create a branch, commit, pull request, or plan file unless the user requested that action or repository instructions explicitly require the artifact.
## Workflow
### 1. Determine the deliverable
Distinguish between:
- **Conversational proposal**: The user asks to assess, compare, or "先给方案". Return the proposal in chat and do not create a file.
- **Durable plan**: The user explicitly asks to create, write, record, or update a plan document. Locate the repository plan directory and write the artifact.
…
The line at the top of this page pins the label git:20260714.ca8d851, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7943 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
GitHub
flc1125/skills · 39 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7zvvyua65fmkf4lc
GET https://markdownregistry.com/api/v1/resolve?ref=flc1125/skills/create-plan
GET https://markdownregistry.com/api/v1/blob/a70df8ed33c84be14278970d97997080c4f135fee86af37c71551addfe2078cf
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.
flc1125/skills · skills/async/SKILL.md · Launch and coordinate Codex subagents as deferred tasks. Use when the user wants to start bounded subagent work now…
flc1125/skills · skills/code-review/SKILL.md · Request or perform a git-backed code review for a defined diff or SHA range using implementation context and…
flc1125/skills · skills/eli5/SKILL.md · Create a simple, picture-first explanation of a topic, defaulting to self-contained HTML. Use when the user says ELI5…
flc1125/skills · skills/engineering-backend-architect/SKILL.md · Design backend system architecture for new products, large features, platform refactors, API and database design…
flc1125/skills · skills/experts/SKILL.md · Assemble a panel of experts to assess a problem from multiple professional perspectives, surface agreement and…
flc1125/skills · skills/getnote/SKILL.md · Save, search, list, and organize Get 笔记 notes, images, tags, and knowledge resources through the Get 笔记 OpenAPI. Use…
flc1125/skills · skills/github-create-pr/SKILL.md · Create GitHub pull requests from a local branch using a reviewable workflow for branch checks, diff analysis, PR…
flc1125/skills · skills/github-renovate-prs/SKILL.md · Inspect, triage, approve, and merge GitHub Renovate pull requests with gh. When no repository is provided, use the…
foryourhealth111-pixel/vibe-skills · bundled/skills/create-plan/SKILL.md · Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
yonatangross/orchestkit · src/skills/create-plan/SKILL.md · Writes an implementation plan as a file artifact in the task directory (.ork/tasks/TASK/NN-plan-SLUG.md) with phases…
yonatangross/orchestkit · plugins/ork/skills/create-plan/SKILL.md · Writes an implementation plan as a file artifact in the task directory (.ork/tasks/TASK/NN-plan-SLUG.md) with phases…
raffertyuy/repo-of-repos · .claude/skills/create-plan/SKILL.md · Create an implementation plan in _plans/ with embedded repo context and step-by-step task lists
raffertyuy/repo-of-repos · .agents/skills/create-plan/SKILL.md · Create an implementation plan in _plans/ with embedded repo context and step-by-step task lists
tomzx/agents · skills/create-plan/SKILL.md · Create an implementation plan with phases, milestones, dependencies, and risks from a specification or requirements…
