implementation-planning SKILL.md skillA
implementation-planning from magnus919/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add magnus919/agent-skills/implementation-planning@git:20260905.2a458abPins git:20260905.2a458ab in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- magnus919/agent-skills
- Path
implementation-planning/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260905.2a458ab, committed Sep 5, 2026
- First version recorded
- Aug 2, 2026
- Size
- 12,297 bytes
- Repository stars
- 140
- License
- MIT
Plan the implementation of an approved requirement or specification: produce an executable, dependency-aware delivery plan covering work breakdown, dependency mapping, critical path, ownership, parallelism and sequencing, rollout strategy, rollback and recovery paths, and verification against the original requirement. Supports cross-team, cross-repository, migration, and staged-rollout scenarios. Do not use for pre-approval discovery or needs-finding, authoring a specification from scratch…
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 Planning Turn an **approved** requirement or specification into an executable delivery plan. This skill is a planning discipline — it produces a plan, not code, not a spec, and not a lifecycle orchestration. ## When to load this skill Load when the input is an **approved requirement, specification, or decision** and the task is to produce a concrete delivery plan that accounts for dependencies, sequencing, risk, and verification. | Trigger | Example | |---|---| | An approved SPEC.md or product brief needs a delivery plan | "Plan the implementation for the payments checkout spec" | | A cross-team or multi-repo feature needs work coordination | "Plan the rollout for the identity-migration change across three services" | | A data migration needs a staged execution plan | "Plan the schema migration with rollback stages" | | A risky or high-stakes change needs a rollout strategy | "Plan the staged rollout for the auth-provider replacement" | | Multiple workstreams need dependency mapping and critical-path analysis | "Map dependencies and critical path for the platform upgrade" | ### When not to use …
Read the whole file at its exact version.
How to install
mdr add magnus919/agent-skills/implementation-planning@sha256:f953b07857dd2f84The line at the top of this page pins the label git:20260905.2a458ab, 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_witqhs6x2i2z4smx)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 2, 2026 and Sep 5, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.2a458ab latest | 2026-09-05 | 2a458ab | 12,297 B | A | view · diff |
| git:20260905.22d141d | 2026-09-05 | 22d141d | 12,099 B | A | view · diff |
| git:20260824.e10508b | 2026-08-24 | e10508b | 11,844 B | A | view · diff |
| git:20260802.f82515e | 2026-08-02 | f82515e | 11,412 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 (12297 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
magnus919/agent-skills · 140 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_witqhs6x2i2z4smx GET https://markdownregistry.com/api/v1/resolve?ref=magnus919/agent-skills/implementation-planning GET https://markdownregistry.com/api/v1/blob/f953b07857dd2f84d038e8243430a299e334fbac1b51481c7d53096a2d27607c
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 magnus919/agent-skills
Every file in magnus919/agent-skills