write-plan SKILL.md skillA
write-plan from cliver-project/cliver is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cliver-project/cliver/write-plan@git:20261025.d71167bPins git:20261025.d71167b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cliver-project/cliver
- Path
packages/cliver/src/cliver/skills/builtin/write-plan/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261025.d71167b, committed Oct 25, 2026
- Size
- 4,072 bytes
- Repository stars
- 8
- License
- Apache-2.0
Create detailed, step-by-step implementation plans from design specs. Use after brainstorming or when you have a spec/requirements for a multi-step task.
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
# Write Plan Create comprehensive implementation plans assuming the engineer has zero context for the codebase but is skilled. Document everything they need: which files to touch, what code to write, how to test, how to verify. Give the whole plan as bite-sized tasks. ## Process ### Step 1: Read the Design Spec If coming from the brainstorm skill, read the design doc from `~/.cliver/temp/design/`. Otherwise, ask the user for the spec or requirements. Use `Read` to load the spec. Understand the goal, architecture, and all changes before writing the plan. ### Step 2: Map the File Structure Before defining tasks, map out which files will be created or modified and what each one is responsible for. - Each file should have one clear responsibility - Files that change together should live together - In existing codebases, follow established patterns - Prefer smaller, focused files over large ones ### Step 3: Break Into Tasks Decompose the work into tasks. Each task is one focused unit — one file or a small group of closely related files. For each task, list concrete steps: - Exact file paths to create or modify - What to change (with specifics, not vague descriptions) …
Read the whole file at its exact version.
How to install
mdr add cliver-project/cliver/write-plan@sha256:920cf22648657831The line at the top of this page pins the label git:20261025.d71167b, 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_jcos4k4y4vpvc7kh)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 25, 2026.
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 (4072 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
cliver-project/cliver · 8 stars · license Apache-2.0 · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jcos4k4y4vpvc7kh GET https://markdownregistry.com/api/v1/resolve?ref=cliver-project/cliver/write-plan GET https://markdownregistry.com/api/v1/blob/920cf226486578315e280619b4ee887c4d868b86417cb8d4e86d102ba637e64e
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 cliver-project/cliver
Every file in cliver-project/cliver