About spec
A development skill that runs the opening phase of roadmap planning and creates or updates a canonical scope document. It clarifies user-visible changes and acceptance examples, then stops before repository design or task planning.
Key features
- 01Loads roadmap instructions and schema
- 02Resolves behavior- and scope-related questions
- 03Writes scope through roadmap.md section 2
- 04Preserves later sections in an existing roadmap
Use cases
- 01Define the user-facing scope of a change
- 02Clarify requirements before repository design
- 03Update an existing roadmap without replacing later sections
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ patrickruddiman/ skills --skill specAfter installing, type/specin Claude Code to confirm it loaded.
Details
From the project READMESpec
Run the opening portion of roadmap, then stop before
repository design.
Workflow
- Load
../roadmap/SKILL.mdand../roadmap/references/roadmap-schema.md. - Apply Roadmap phase 1. Recommend direct implementation for trivial work unless the user explicitly requests a written artifact.
- Resolve only questions that change user-visible behavior or scope. Ask at most three; use the simplest stated default for everything else.
- Write or update the canonical
roadmap.mdthrough## 2. Scope. - Stop. Do not choose files, libraries, architecture, verticals, or tasks.
Compatibility
- If a repository already standardizes on
spec.mdorprd.md, update that artifact rather than creating a duplicate. - If
roadmap.mdalready exists, preserve its later sections. - A later
/roadmapinvocation resumes with repository recon.
Rules
- Describe WHAT changes for a user and WHY.
- Use concrete acceptance examples.
- Do not invent personas, modes, lifecycle states, quality bars, or exclusions.
- No code, paths, libraries, schemas, architecture, rollout, or task breakdown.
Comments
Markdown supported