feature-planning-handsoff SKILL.md skillA
feature-planning-handsoff 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-handsoff@git:20261103.e618ac3Pins git:20261103.e618ac3 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-handsoff/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261103.e618ac3, committed Nov 3, 2026
- First version recorded
- Nov 3, 2026
- Size
- 7,305 bytes
- Repository stars
- 3
- License
- MIT
Plan a feature without the owner in the loop — you answer every round of questions as the designer and one outside reviewer (another vendor's model when available) checks each round, decisions that belong to the owner are marked as assumed, and the plan comes out provisionally approved, optionally going straight on to be built. Use when the owner wants a feature planned (and possibly built) while they are away — when they invoke it, ask for hands-off planning in their own words, or accept it…
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 (hands-off) Load the **`feature-planning-core`** skill (`game-sdlc:feature-planning-core` when installed as a plugin) and follow it in **hands-off mode**: you and one round reviewer answer the rounds instead of the owner. The ledger still calls the two of you "the panel". ## 1. The one question asked up front Before the owner leaves, ask a single question — what happens after the plan: 1. **Stop at the plan** — the owner reads the ledger and decides. 2. **Build it with `team-lead`** (recommended) — PRs wait for the owner to merge. 3. **Build it with `team-lead-handsoff`** — reviewed PRs merge to `main` without the owner. Everything after that runs without asking. - If the owner is already gone, take option 1. - If there's no taste profile, offer it with this question, while the owner is still there (`taste-profile` §5). ## 2. You and the round reviewer **You are the designer.** Write each round as you would for the owner (core §3): the frontier, and a recommendation per question, consistent with the rest of the game. Under each recommendation, write `Pillar test:` and the pillar test question it passes. …
Read the whole file at its exact version.
How to install
mdr add amramos/game-ai-sdlc/feature-planning-handsoff@sha256:fadf49031b11919eThe line at the top of this page pins the label git:20261103.e618ac3, 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_mlielo6zlp7cbtwf)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Nov 3, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261103.e618ac3 latest | 2026-11-03 | e618ac3 | 7,305 B | A | view · diff |
| git:20261103.cac3e99 | 2026-11-03 | cac3e99 | 7,204 B | A | view · diff |
| git:20261103.84aa016 | 2026-11-03 | 84aa016 | 9,228 B | A | view · diff |
| git:20261103.c1330ed | 2026-11-03 | c1330ed | 9,101 B | A | view · diff |
| git:20261103.fcbf531 | 2026-11-03 | fcbf531 | 9,025 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 (7305 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_mlielo6zlp7cbtwf GET https://markdownregistry.com/api/v1/resolve?ref=amramos/game-ai-sdlc/feature-planning-handsoff GET https://markdownregistry.com/api/v1/blob/fadf49031b11919e0e2f87a93a1b1a12ce21f891c6e96fb1e03835a09ca8223c
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.