dist/codex/plugins/spec-dev/skills/spec-new/SKILL.md
Create a single TASK or REQ file from a template. Use for one-off artifact creation without the full planning workflow. NOT for full project bootstrap (spec-init) or multi-task planning from a requirement (spec-plan).
npx skillsauth add alexei-led/claude-code-config spec-newInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
spec new — create a single task or req from templateCLI at scripts/specctl. Input: <type> <name> where <type> is task or req. If <name> contains /, the leading part is a topic folder.
Validate before doing any work:
<name>: ask for the name; do not invent a placeholder.<type> not task or req: state the allowed values and stop; do not guess..spec/ existsls .spec/ 2>/dev/null || mkdir -p .spec/tasks .spec/reqs
task <name> → .spec/tasks/TASK-<name>.mdtask <topic>/<name> → .spec/tasks/<topic>/TASK-<name>.mdreq <name> → .spec/reqs/REQ-<name>.mdreq <topic>/<name> → .spec/reqs/<topic>/REQ-<name>.md---
id: TASK-<name>
status: todo
priority: normal
implements:
---
# <Title>
(Describe the vertical slice, acceptance criteria, and out-of-scope boundaries.)
---
id: REQ-<name>
version: 1
priority: normal
---
# <Title>
(Describe requirements and success criteria.)
Write the file, then append to the progress log:
echo "$(date +%H:%M) NEW <TYPE>-<name>" >> .spec/PROGRESS.md
Output:
Created: .spec/<type>s/<TYPE>-<name>.md
tools
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.
development
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
tools
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).
tools
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, Rust, TypeScript, Go, web code, or GitHub Actions workflow/job/permissions semantics; use operating-infra.