Management & product · Planning
plan-feature
/plan-feature
Plan a new Roastpilot feature spec-first. Use when asked to add or change behaviour, before writing code.
For whom
- Author
- mnabaci ↗
- Repository
- Roastpilot ↗
- Licence
- GPL-3.0
- Last repository change
- 11.11.2026
Assessment and security
86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
Licence
GPL-3.0, otwarta.
What it does and when to use it
Plan a new Roastpilot feature spec-first. Use when asked to add or change behaviour, before writing code.
Original author description
Plan a new Roastpilot feature spec-first. Use when asked to add or change behaviour, before writing code.
How it works
SKILL.md has no level-two headings · 12 lines, 154 words
SKILL.md preview
--- name: plan-feature description: Plan a new Roastpilot feature spec-first. Use when asked to add or change behaviour, before writing code. --- # Plan a feature 1. Restate the feature in one sentence and list what the user will see or do. Run `challenge` on it first; a concern is settled with the user before planning. 2. Read the affected `docs/spec/*.md` files and the root `AGENTS.md`. 3. Ask the user only about choices that change behaviour; propose a recommended option for each. 4. Update the spec: edit the right file(s) in `docs/spec/`, keep the style (tables, short bullets, no walls of text). Add a new file only for a new area, and link it from `docs/spec/README.md`. 5. If a choice is hard to reverse (new dependency, data model shape, new extension point), write an ADR from `docs/adr/template.md` and link it in `docs/adr/README.md`. 6. Write a task list: one task per package touched, in dependency order (`shared` → `core` → `drivers`/`storage` → `ui` → `apps/desktop`), each with its tests. 7. Stop and show the plan before implementing.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mnabaci/Roastpilot | 86 | GPL-3.0 |
| arozumenko/sdlc-skills | 100 | MIT |
| trihuynh-agilityio/workez | 100 | MIT |
| arozumenko/sdlc-skills | 100 | MIT |
| mo-cmyk/mazarbul | 100 | Apache-2.0 |
| smartwhale8/claude-playbook | 100 | MIT |
| arozumenko/wikis | 100 | MIT |
| Shoebtamboli/rails_claude_skills | 100 | MIT |
| mnzralee/claude-multi-agent-architecture | 90 | MIT |
Database snapshot: 13.11.2026 · package version fdf19d33d383 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100contract-first
Turn a feature request, behaviour change, or removal into an agreed behaviour contract before any code is written. Use whenever the user says "I want", "let's add", "can we make it", "change how X works", or "remove Y", and whenever requirements are loose, even if they do not… - 86add-component
Add or change a Roastpilot UI component in packages/ui, keeping the design system in step. Use when a screen needs a reusable piece of UI, or an existing component's look, sizes or rules change. - 100engineering-standards
The Roastpilot coding checklist. Use before writing or changing any code in this repo, and whenever unsure how something should be structured. - 90pfb-spec-new
Draft a new feature specification (requirements.md, design.md, tasks.md) in specs/NNNN-feature-name/ through an iterative question-first conversation. Use when the user wants to spec, scope or plan a new feature before writing code. - 90write-spec
Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing. - 841-plan
Plans a feature or phase — drafts and refines its specification with the user, from a GitHub issue, their own draft or a conversation, then plans the work into SPEC.md, with a lighter route for a small, clear change. Invoked when the user wants to plan a feature, write or refine…