feature-planning-core SKILL.md skillA
feature-planning-core from amramos/game-ai-sdlc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amramos/game-ai-sdlc/feature-planning-core@git:20261104.14f7bccPins git:20261104.14f7bcc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amramos/game-ai-sdlc
- Path
plugins/game-sdlc/skills/feature-planning-core/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261104.14f7bcc, committed Nov 4, 2026
- First version recorded
- Nov 3, 2026
- Size
- 17,099 bytes
- Repository stars
- 3
- License
- MIT
The shared method behind feature-planning and feature-planning-handsoff — rounds of questions over a design tree, a player walkthrough, sketches for layout decisions, a decisions ledger the owner approves, the plan agents build from, and a two-way check that the plan holds every decision and invents none. Loaded by those two skills; not called directly by 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
# Feature planning: the shared method This closes the gap between "the plan contains the decision" and "the owner understood and approved the result". A plan can be technically sound and still describe a different game from the one the owner has in mind; a fully built, fully tested feature rejected on first play is the failure this exists to prevent. The method is the same in both modes. Only **who answers the rounds** differs: - **interactive** (`feature-planning`): the owner answers; - **hands-off** (`feature-planning-handsoff`): you answer with one outside reviewer per round, and the owner reads the result later. Two documents come out of it, for two readers: - the **decisions ledger** — short, for the owner: every decision, who made it, and the walkthrough, sketches and approval record. **This is what the owner approves.** - the **plan** — long, for agents: requirements, architecture, work packages, traceability. **The owner's taste profile.** Before the first round, read it by `taste-profile` §1 (`game-sdlc:taste-profile` when installed as a plugin): - **Never open `taste.md` yourself; run §1's command**, which prints only the Never lines. You write …
Read the whole file at its exact version.
How to install
mdr add amramos/game-ai-sdlc/feature-planning-core@sha256:d5ee863b497994bcThe line at the top of this page pins the label git:20261104.14f7bcc, 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_gnd24ulommhnh3cz)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Nov 3, 2026 and Nov 4, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261104.14f7bcc latest | 2026-11-04 | 14f7bcc | 17,099 B | A | view · diff |
| git:20261103.d7e3f45 | 2026-11-03 | d7e3f45 | 16,884 B | A | view · diff |
| git:20261103.a4c5a1d | 2026-11-03 | a4c5a1d | 16,779 B | A | view · diff |
| git:20261103.160789c | 2026-11-03 | 160789c | 16,484 B | A | view · diff |
| git:20261103.7fc0cad | 2026-11-03 | 7fc0cad | 13,531 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 (17099 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
amramos/game-ai-sdlc · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gnd24ulommhnh3cz GET https://markdownregistry.com/api/v1/resolve?ref=amramos/game-ai-sdlc/feature-planning-core GET https://markdownregistry.com/api/v1/blob/d5ee863b497994bc4a5d4751087f6361c2e6134864ed54cbf4bfa000b19e2654
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.