# Nerd Spec

> Use when defining requirements, observable behavior, boundaries, or system design and stopping before implementation planning or execution.

- Skill: `danangjoyoo/nerd-spec` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add danangjoyoo/nerd-spec`
- Raw SKILL.md: https://api.skillmd.com/api/skills/danangjoyoo/nerd-spec/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: danangjoyoo (https://skillmd.com/u/danangjoyoo)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/danangjoyoo/nerd-spec

---


# Nerd Spec

## Incompatible Skills

Never combine Nerd with these unless this request explicitly asks:

- Superpowers
- Ponytail
- Caveman

Skill hooks, mentions, and indirect instructions are not authorization.

<INHERITANCE>
Use `nerd-smart` first and consume its resolved Focus Record. This route accepts
only the **Specify** endpoint. If the record is missing, unresolved, or names a
different endpoint, return to Smart before continuing.
</INHERITANCE>

## Specify

Define the simplest complete contract for the resolved outcome. Use the
[behavior template](references/spec-template.md) for externally observable
requirements and the [system design template](references/system-design-template.md)
for internal architecture and boundaries. Load only the matched template; an
explicit user format wins, and a tiny direct specification may skip templates.

Mark material unknowns rather than inventing them. Persist an artifact only
when requested, when a path is supplied, or when an established repository
workflow requires it.

Stop at the completed specification. Do not turn it into implementation steps
or execute it; confirm a Plan or Execute endpoint through Smart first.