ce-plan SKILL.md skillA
ce-plan from shyamsridhar123/kevin-copilot is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shyamsridhar123/kevin-copilot/ce-plan@git:20260422.d562cf9Pins git:20260422.d562cf9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shyamsridhar123/kevin-copilot
- Path
.github/skills/ce-plan/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260422.d562cf9, committed Apr 22, 2026
- Size
- 62,117 bytes
- Repository stars
- 8
- License
- MIT
Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Use for plan deepening when the user…
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 Technical Plan **Note: The current year is 2026.** Use this when dating plans and searching for recent documentation. `ce-brainstorm` defines **WHAT** to build. `ce-plan` defines **HOW** to build it. `ce-work` executes the plan. This workflow produces a durable implementation plan. It does **not** implement code, run tests, or learn from execution-time results. If the answer depends on changing code and seeing what happens, that belongs in `ce-work`, not here. ## Interaction Method Use the platform's question tool when available. When asking the user a question, prefer the platform's blocking question tool if one exists (`AskUserQuestion` in Claude Code, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in chat and wait for the user's reply before proceeding. Ask one question at a time. Prefer a concise single-select choice when natural options exist. ## Feature Description <feature_description> #$ARGUMENTS </feature_description> **If the feature description above is empty, ask the user:** "What would you like to plan? Please describe the feature, bug fix, or improvement you have in mind." …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_f3to7qgm4vnxmgob/59ec493d11c7d1048ab23d3b3fc6e11142dca33767c0e47d70b2d3da50bf3d1b.json
Then /plugin install ce-plan@markdownregistry-f3to7qgm4vnxmgob in Claude Code. It installs git:20260422.d562cf9, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shyamsridhar123/kevin-copilot/ce-plan@sha256:59ec493d11c7d104The line at the top of this page pins the label git:20260422.d562cf9, 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_f3to7qgm4vnxmgob)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in shyamsridhar123/kevin-copilot/ce-plan since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of ce-plan from somewhere else? Ask it: where did my ce-plan come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Apr 22, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/ce-plan/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (62117 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
shyamsridhar123/kevin-copilot · 8 stars · license MIT · pushed 2026-08-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_f3to7qgm4vnxmgob GET https://markdownregistry.com/api/v1/resolve?ref=shyamsridhar123/kevin-copilot/ce-plan GET https://markdownregistry.com/api/v1/blob/59ec493d11c7d1048ab23d3b3fc6e11142dca33767c0e47d70b2d3da50bf3d1b
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.
More from shyamsridhar123/kevin-copilot
Every file in shyamsridhar123/kevin-copilot
Other files named ce-plan
Browse by kind, by grade A, or by owner.
Kept in .github/skills, the folder GitHub Copilot reads. More agent skills for GitHub Copilot.