skills.rest
brayandiazc
brayandiazcCOMMUNITY
Explore all skills by this author →
Website𝕏@brayandiazcGitHub

new-spec

Creates a numbered change specification directory from a template and links it to the product roadmap.

15|22|Updated May 5, 2024
Search Tags:#planning#specification#feature design#roadmap#change proposal#template scaffolding
One-click install
npx skills add https://github.com/brayandiazc/project-starter-template-es-ai --skill new-spec-brayandiazc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-spec
Source: https://github.com/brayandiazc/project-starter-template-es-ai/tree/main/.claude/skills/new-spec
Command: npx skills add https://github.com/brayandiazc/project-starter-template-es-ai --skill new-spec-brayandiazc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new feature or change without a written specification leads to untracked decisions and misaligned implementation. This Skill scaffolds a lightweight change specification so planning happens before code is written. ## Core Features & Use Cases - Spec Scaffolding: Copies the specs/_template directory into a new specs/NNNN-<change-name>/ folder with an auto-incremented four-digit prefix. - Metadata Pre-fill: Fills in the change title, Draft status, and current date, leaving problem, goals, and approach sections as author prompts. - Roadmap Linkage: Reads docs/product/roadmap.md and binds the spec to a specific roadmap item, annotating the roadmap entry with the spec path. - Use Case: Before implementing a checkout redesign, run the Skill to create specs/0007-checkout-redesign/ with proposal, design, and tasks files ready to complete, ensuring the branch guardrail hook allows code edits later. ## Quick Start Ask the assistant to create a new spec for the change you want to plan, for example by saying create a spec for the checkout redesign.

Frequently Asked Questions about new-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new change specification before implementing a feature?▼

Invoke the Skill with a change name, such as /new-spec checkout redesign. It copies specs/_template into a new specs/NNNN-<slug>/ directory, fills in the title, Draft status, and date, and reports which files still need completion.

How is the spec folder number NNNN calculated?▼

The Skill scans specs/ and specs/archive/ for the highest existing four-digit numeric prefix and adds one. If no numbered spec exists yet, it starts at 0001.

Does the spec need to be linked to the product roadmap?▼

Yes. The Skill reads docs/product/roadmap.md and fills the roadmap item field in proposal.md, then annotates the roadmap entry with the spec path. If no item fits, it flags that the change should be added or reconsidered.

What happens if a spec with the same name already exists?▼

The Skill stops and asks instead of overwriting. It checks for any existing specs/*-<change-name>/ directory with any numeric prefix and never deletes or replaces an existing specification folder.

Why must the spec be created before the implementation branch?▼

A spec-guardrails hook blocks code edits on feat/* or fix/* branches whose matching spec does not exist or still contains unfilled template lines. Creating the spec first ensures the branch passes the guardrail checks.

Related Skills

Explore More Product & Management Skills→
ChazzCoinChazzCoin

mvp

Plan and define a Minimum Viable Product with scoping and phased task artifacts.

Community
Advanced
hiro1989hiro1989
1

openspec-verify-change

Verifies code implementations match specified change artifacts using openspec CLI.

Community
Advanced
josemartinrodriguezmortalonijosemartinrodriguezmortaloni

sdd-archive

Sync delta specifications into main specs and archive change folders.

Community
Advanced
chohra-medchohra-med
28

spec-harness-tickets

Convert ticket tracker issues and ad-hoc plans into structured spec documents.

Community
Advanced