spec new

Reference

Create the next specification document under dirs.specs (numbered Markdown with YAML frontmatter). The frontmatter is filled from the spec-metadata schema defaults; the spec id and creation date are set automatically from the next number in the sequence and today's date. Flags override individual fields, and on an interactive terminal any field left unset is collected through an inline themed form that includes a multi-line body editor. With --yes (or when there is no terminal) the file is written from defaults plus flags, --title is required, and the starter skeleton body is used unless --body is given.

Optional

Spec title; also the source of the filename slug unless --slug is given.

Filename slug (overrides the title-derived slug); must match ^[a-z0-9][a-z0-9-]*$.

One-paragraph summary of the spec.

Parent spec id like #0002; repeatable.

Lowercase topic tag; repeatable.

Advisory repository-relative directory this spec targets.

Markdown body written below the frontmatter (default: skeleton template).

Non-interactive: never prompt (requires --title).

Usage

# Usage
overplane spec new [--title TITLE] [--slug SLUG] [--description DESC] [--parent ID]... [--tag TAG]... [--target-dir DIR] [--body BODY] [--yes]

# Examples
# Create the next spec, prompting for any unset fields.
$ overplane spec new --title "My Spec"
# Create a spec non-interactively from flags.
$ overplane spec new --title "Auth" --parent '#0002' --tag cli --yes
# Create a spec with a custom Markdown body.
$ overplane spec new --title "Notes" --body "# Notes\n\nShip it." --yes

internal/cli/speccmd.go