plan SKILL.md skillA
plan from lamngockhuong/aiteamkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lamngockhuong/aiteamkit/plan@git:20261106.96eea03Pins git:20261106.96eea03 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lamngockhuong/aiteamkit
- Path
plugins/atk/skills/plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261106.96eea03, committed Nov 6, 2026
- First version recorded
- Oct 1, 2026
- Size
- 18,103 bytes
- Repository stars
- 12
- License
- MIT
Turn a piece of work into phases and steps: today's code with file paths, phases that each end in something reviewable, steps that leave the tree working and how each is checked, what is out of scope, and what is unclear with who must answer. Also reviews a written plan against the repository and the request, challenges it with one agent per way it can fail, and records the answers to its open questions. Use before starting work, on work somebody else designed, when work needs stages but one…
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 Plan (`atk:plan`) Answers one question: for this work, which files, in which order, checked how. It is the layer between the design and the code, written by the person who will do the work, for that person and their reviewer. Work that needs several days and several reviewable pieces gets several phases, in one plan directory. Nobody has to chop a piece of work into small tickets before they are allowed to plan it: finding where the seams are is what this skill is for. The plan is a draft and acting on it needs nobody's approval. Writing down the steps you intend to take is drafting, not deciding, so rule 3 in `shared/team-roles.md` does not bite here. What needs approval is an architectural choice, and choosing between architectures is `atk:design-doc`. When this skill finds it is comparing approaches rather than sequencing one, it has crossed into that skill's work and says so. ## Scope Handles: reading the ticket or description and any design it points at, scanning the repository for what exists today, cutting the work into phases that each end in something mergeable, sequencing …
Read the whole file at its exact version.
How to install
mdr add lamngockhuong/aiteamkit/plan@sha256:bf6f9a339101e22eThe line at the top of this page pins the label git:20261106.96eea03, 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_idejw46ezazwj6uk)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 1, 2026 and Nov 6, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.96eea03 latest | 2026-11-06 | 96eea03 | 18,103 B | A | view · diff |
| git:20261014.03c655e | 2026-10-14 | 03c655e | 18,475 B | A | view · diff |
| git:20261002.22b4c08 | 2026-10-02 | 22b4c08 | 18,269 B | A | view · diff |
| git:20261001.3822017 | 2026-10-01 | 3822017 | 18,540 B | A | view · diff |
| git:20261001.ed02384 | 2026-10-01 | ed02384 | 17,999 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 (18103 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
lamngockhuong/aiteamkit · 12 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_idejw46ezazwj6uk GET https://markdownregistry.com/api/v1/resolve?ref=lamngockhuong/aiteamkit/plan GET https://markdownregistry.com/api/v1/blob/bf6f9a339101e22eda4b4808455c73f54af02d44ab1a7483907a8aec93f73571
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 lamngockhuong/aiteamkit
Every file in lamngockhuong/aiteamkit