implementation-planner SKILL.md skillA
implementation-planner from pantheon-org/tekhne is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pantheon-org/tekhne/implementation-planner@v3.0.0Pins v3.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pantheon-org/tekhne
- Path
skills/project-mgmt/planning-toolkit/implementation-planner/SKILL.md- Versions recorded
- 2
- Latest version
- v3.0.0, committed Sep 23, 2026
- First version recorded
- Apr 6, 2026
- Size
- 18,172 bytes
- Repository stars
- 10
- License
- MIT
Converts a PRD or requirements document into a structured, phased implementation plan with individual phase files and granular per-task files written to .context/plans/. Also restructures existing monolithic planning documents into digestible, hierarchical directory structures. Creates a root plan index summarising all phases, a numbered phase file per phase, and a numbered task file per task inside each phase directory. Use when the user asks to create an implementation plan, break down a…
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
# Implementation Planner ## Mindset An implementation plan is a **navigable contract between an agent and a codebase**. Each file answers a single question: "What do I need to do next, how do I do it, and how do I prove it is done?" Two failure modes to avoid: 1. **The monolith** — one giant plan.md nobody reads because everything is in one file 2. **The skeleton** — directories with empty READMEs that give no useful signal The sweet spot is a tree where every node either navigates (README) or implements (task file), and every leaf has a runnable verification command. ## Quick Start **Mode 1 — Create a new plan from a PRD:** ```sh sh scripts/new-plan.sh url-shortener-service sh scripts/new-phase.sh url-shortener-service 01 workspace-bootstrap sh scripts/new-task.sh url-shortener-service 01 01 initialise-npm-package sh scripts/validate-plan.sh url-shortener-service ``` **Mode 2 — Split a monolithic document:** ```sh # 1. Create hierarchy manually (steps below) or from JSON: sh scripts/generate-structure.sh --plan plan.json # 2. Validate before removing source sh scripts/validate-structure.sh docs/refactoring/phases ``` ## When to use each mode | Signal | Mode | …
Read the whole file at its exact version.
How to install
mdr add pantheon-org/tekhne/implementation-planner@sha256:0655b5aedcfb5950The line at the top of this page pins the label v3.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.
[](https://markdownregistry.com/a/art_r35njrujyj4uqsfm)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 6, 2026 and Sep 23, 2026, about one every 170 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.0.0 latest | 2026-09-23 | 7852cb4 | 18,172 B | A | view · diff |
| v3.0.0 | 2026-04-06 | 2f91c1b | 18,238 B | A | view |
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 (18172 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
pantheon-org/tekhne · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r35njrujyj4uqsfm GET https://markdownregistry.com/api/v1/resolve?ref=pantheon-org/tekhne/implementation-planner GET https://markdownregistry.com/api/v1/blob/0655b5aedcfb595058429204e03d8635ea300c6e075b724d9d1db5ba9bda40e4
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.