spec-plan SKILL.md skillA
spec-plan from martinffx/atelier is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add martinffx/atelier/spec-plan@git:20261017.81dd276Pins git:20261017.81dd276 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- martinffx/atelier
- Path
skills/spec-plan/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261017.81dd276, committed Oct 17, 2026
- First version recorded
- Jul 31, 2026
- Size
- 13,963 bytes
- Repository stars
- 48
- License
- MIT
Write approved implementation plans in one of two modes. Explicit Inline mode creates a conversational plan for bounded work. Spec-backed Plan converts an approved design.md into plan.json. Both modes stop after producing their plan output. Trigger after atelier-orchestrator selects a mode, when the user asks to plan work, or after spec-brainstorm completes. Direct invocation without a selected mode uses Spec-backed Plan. Do NOT use for research or execution.
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
# Spec Plan Write a proportional plan so clear that any engineer can follow it. The selected planning mode determines whether the plan stays in the conversation or becomes a persisted structured artifact. This skill does not write code or start implementation. `atelier-orchestrator` owns automatic classification and the human may override it. When this skill is directly invoked without a selected mode, use Spec-backed Plan. If Inline planning reveals substantial design or coordination needs, ask the human whether to switch to a Spec-backed Plan before presenting the plan. ## Terminal boundary This skill produces exactly one plan output and then stops: - Inline mode presents the plan in conversation and changes no repository files. - Spec-backed mode creates or updates only `plan.json` from an approved `design.md`. Planning drafts and annotation cycles stay in conversation. Do not modify `design.md`, persist a Markdown plan draft, create tracker entries, invoke another workflow skill, or edit implementation files. These rules still apply when the human asks to plan and implement in one request. Implementation requires a later, explicit request after this skill has finished. …
Read the whole file at its exact version.
How to install
mdr add martinffx/atelier/spec-plan@sha256:5d446ea0ff59e14aThe line at the top of this page pins the label git:20261017.81dd276, 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_kvhuu3ogpgbthvor)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Jul 31, 2026 and Oct 17, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.81dd276 latest | 2026-10-17 | 81dd276 | 13,963 B | A | view · diff |
| git:20261009.3672e9c | 2026-10-09 | 3672e9c | 14,020 B | A | view · diff |
| git:20261009.81af084 | 2026-10-09 | 81af084 | 13,933 B | A | view · diff |
| git:20260809.2626d8c | 2026-08-09 | 2626d8c | 12,819 B | A | view · diff |
| git:20260809.fcf852b | 2026-08-09 | fcf852b | 12,762 B | A | view · diff |
| git:20260801.96f6fe8 | 2026-08-01 | 96f6fe8 | 10,592 B | A | view · diff |
| git:20260731.112e30a | 2026-07-31 | 112e30a | 10,171 B | A | view · diff |
| git:20260731.12256e1 | 2026-07-31 | 12256e1 | 10,614 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 (13963 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
martinffx/atelier · 48 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kvhuu3ogpgbthvor GET https://markdownregistry.com/api/v1/resolve?ref=martinffx/atelier/spec-plan GET https://markdownregistry.com/api/v1/blob/5d446ea0ff59e14a59aa53fd27e3ce60385b579de9c603bcaea15f0018e73847
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.