spec-newlisted

# `spec new` — create a single task or req from template CLI at `scripts/specctl`. Input: `<type> <name>` where `<type>` is `task` or `req`. If `<name>` contains `/`, the leading part is a topic folder. ## Failure handling Validate before doing any work: - Missing or empty `<name>`: ask for the name; do not invent a placeholder. - `<type>` not `task` or `req`: state the allowed values and stop; do not guess. - Target file already exists: do not overwrite. Report the existing path and ask whether to open it, pick a new name, or confirm overwrite. ## Step 1: Ensure `.spec/` exists ```bash ls .spec/ 2>/dev/null || mkdir -p .spec/tasks .spec/reqs ``` ## Step 2: Determine path - `task <name>` → `.spec/tasks/TASK-<name>.md` - `task <topic>/<name>` → `.spec/tasks/<topic>/TASK-<name>.md` - `req <name>` → `.spec/reqs/REQ-<name>.md` - `req <topic>/<name>` → `.spec/reqs/<topic>/REQ-<name>.md` ## Step 3: Generate content ### Task template ```markdown --- id: TASK-<name> status: todo priority: normal implements: --- # <Title> (Describe the vertical slice, acceptance criteria, and out-of-scope boundaries.) ``` ### Req template ```markdown --- id: REQ-<name> version: 1 priority: normal --- # <Title> (Describe requirements and success criteria.) ``` ## Step 4: Write + log Write the file, then append to the progress log: ```bash echo "$(date +%H:%M) NEW <TYPE>-<name>" >> .spec/PROGRESS.md ``` Output: ``` Created: .spec/<type>s/<TYPE>-<name>.md ```