How do I install the Spec New skill?

Run npx skillmds@latest add lucassantana-dev/spec-new in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Spec New skill do?

Create a committed per-feature spec under `docs/specs/YYYY-MM-DD- /{spec,tasks}.md` with frontmatter (status, created, owner, pr, tags). Promotes an ephemeral `.claude/plans/ .md` into a persistent, searchable artifact. Use when starting a feature that's larger than a one-shot PR. It is listed under Coding & Dev Tools on SkillMD.

Is Spec New safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec New?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec New free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec New?

LucasSantana-Dev (@lucassantana-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec New by lucassantana-dev — Agent Skill

Name: Spec New
Rating: 4.666666666666667 (3 reviews)
Author: LucasSantana-Dev

Spec New

Create a committed per-feature spec under `docs/specs/YYYY-MM-DD-<slug>/{spec,tasks}.md` with frontmatter (status, created, owner, pr, tags). Promotes an ephemeral `.claude/plans/<name>.md` into a persistent, searchable artifact. Use when starting a feature that's larger than a one-shot PR.

LucasSantana-Dev Updated Aug 19, 2026 1 repo stars

File contents

spec-new

Agent-OS-style spec creation, adapted to our stack.

When to use

A plan in ~/.claude/plans/ is ready to execute AND will span multiple sessions or PRs.
User asks "let's formalize this / make a spec for it".
You're about to create a branch that will take more than one session.

When NOT to use

One-session quick fix → just commit, no spec.
Research/brainstorm that may not ship → leave as plan.

Usage

~/.claude/rag-index/venv/bin/python ~/.claude/rag-index/specs.py new "<slug>" \
  --repo <path-to-repo> \
  [--from-plan ~/.claude/plans/<file>.md] \
  [--tags "rag,platform"]

Outputs a new folder docs/specs/<date>-<slug>/ containing:

spec.md — goal + context + approach + verification, with YAML frontmatter (status: proposed by default).
tasks.md — checkbox list. If --from-plan was used, headers like ### Phase N become tasks automatically.

Typical flow

Draft plan in ~/.claude/plans/<name>.md via plan skill.
spec-new <slug> --from-plan ... commits it to the repo.
Work through tasks.md across sessions. Tick boxes as they land.
When all tasks are ✓ and PR merged → use spec-ship.
Periodically regenerate docs/roadmap.md via roadmap-refresh.

Integration with RAG

Specs index under source_type=spec, roadmaps under source_type=roadmap. Retrieve related past specs before drafting:

~/.claude/rag-index/venv/bin/python ~/.claude/rag-index/query.py --scope spec "<new feature summary>"

---name: spec-newdescription: Create a committed per-feature spec under `docs/specs/YYYY-MM-DD-<slug>/{spec,tasks}.md` with frontmatter (status, created, owner, pr, tags). Promotes an ephemeral `.claude/plans/<name>.md` into a persistent, searchable artifact. Use when starting a feature that's larger than a one-shot PR.---# spec-newAgent-OS-style spec creation, adapted to our stack.## When to use- A plan in `~/.claude/plans/` is ready to execute AND will span multiple sessions or PRs.- User asks "let's formalize this / make a spec for it".- You're about to create a branch that will take more than one session.## When NOT to use- One-session quick fix → just commit, no spec.- Research/brainstorm that may not ship → leave as plan.## Usage```bash~/.claude/rag-index/venv/bin/python ~/.claude/rag-index/specs.py new "<slug>" \ --repo <path-to-repo> \ [--from-plan ~/.claude/plans/<file>.md] \ [--tags "rag,platform"]```Outputs a new folder `docs/specs/<date>-<slug>/` containing:- `spec.md` — goal + context + approach + verification, with YAML frontmatter (`status: proposed` by default).- `tasks.md` — checkbox list. If `--from-plan` was used, headers like `### Phase N` become tasks automatically.## Typical flow1. Draft plan in `~/.claude/plans/<name>.md` via `plan` skill.2. `spec-new <slug> --from-plan ...` commits it to the repo.3. Work through `tasks.md` across sessions. Tick boxes as they land.4. When all tasks are ✓ and PR merged → use `spec-ship`.5. Periodically regenerate `docs/roadmap.md` via `roadmap-refresh`.## Integration with RAGSpecs index under `source_type=spec`, roadmaps under `source_type=roadmap`. Retrieve related past specs before drafting:```bash~/.claude/rag-index/venv/bin/python ~/.claude/rag-index/query.py --scope spec "<new feature summary>"```## See also- `spec-ship` — archive a shipped spec.- `roadmap-refresh` — regenerate `docs/roadmap.md` from spec frontmatters.- `plan` — ephemeral session planning.

Frequently asked questions