plan SKILL.md skillA

plan from bluestep-systems/bluestep-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add bluestep-systems/bluestep-ai/plan@git:20261103.5c82982

Pins git:20261103.5c82982 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

bluestep-systems/bluestep-ai

Path

plugins/core-tools/skills/plan/SKILL.md

Versions recorded

1

Latest version

git:20261103.5c82982, committed Nov 3, 2026

Size

4,957 bytes

Repository stars

3

License

none declared

Start a spec for work that needs design. Writes requirements.md, then design.md, then tasks.md under .claude/specs/<feature>/, with explicit approval between each. Use when the user wants to plan a feature or a change that touches several parts of a repo; for a small scoped change, use /task.

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

# /plan — requirements, design, tasks

A spec lives at `.claude/specs/<feature>/` as three files. Each phase needs explicit approval
before the next. The point is a self-contained spec: it names the files and interfaces involved,
says what is out of scope, and ends with a check that proves the whole thing works. Once it is
approved, implementation runs from the spec alone, so a session can stop and a later one pick up.

## Phase 0 — setup

1. Ask for the **feature name** (kebab-case) and a **one-line description**.
2. If a ticket system MCP is available and the user has a ticket, offer to seed from it. Fetch
   only the description, not the whole thread.
3. Create `.claude/specs/<feature>/`.

## Phase 1 — requirements

1. Copy `${CLAUDE_PLUGIN_ROOT}/skills/plan/templates/requirements.template.md` to
   `.claude/specs/<feature>/requirements.md` and fill it in.
2. **STOP.** Say: "Requirements drafted at `.claude/specs/<feature>/requirements.md`. Review and
   approve before I go on to design." Wait for an explicit yes.

## Phase 2 — design

1. Read the parts of the repo the feature touches, scoped: grep for the symbols and read the
…

Read the whole file at its exact version.

How to install

mdr add bluestep-systems/bluestep-ai/plan@sha256:53e3468d57ed78d2

[![mdr](https://markdownregistry.com/badge/art_5kqigflzomqqe2z4.svg)](https://markdownregistry.com/a/art_5kqigflzomqqe2z4)

Versions

The registry has recorded 1 version of this file, committed on Nov 3, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_5kqigflzomqqe2z4
GET https://markdownregistry.com/api/v1/resolve?ref=bluestep-systems/bluestep-ai/plan
GET https://markdownregistry.com/api/v1/blob/53e3468d57ed78d20cbc28db0a9df4805981ea50fdcb4adc1560429485a4ae2a

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 bluestep-systems/bluestep-ai

Every file in bluestep-systems/bluestep-ai

Other files named plan

Browse by kind, by grade A, or by owner.