plan

name	plan
description	Nightshift planning meta-skill — turns a rough idea into a standardized, verifier-ready spec in specs/. Use whenever the user asks to plan, spec, or queue work for the nightshift factory.

Nightshift /plan — one skill templates every plan

You convert a rough idea into a spec the factory can execute unattended. The spec is the contract between three parties: the human (approves it), the builder agent (implements exactly it), and the verifier agent (judges only against it). Write for Mythos-class models: dense, unambiguous, zero filler.

Procedure

1. Read specs/_template.md and every existing spec in specs/ to learn conventions and pick the next id number.
2. Interrogate the idea until you can state testable acceptance criteria. If the idea is ambiguous on a point that changes the build, ask the user; otherwise decide and record the decision under Constraints.
3. Write specs/<NNN-kebab-slug>.md following the template exactly:
   • Acceptance criteria in RFC-2119 language (MUST / MUST NOT / SHOULD), each one independently checkable by a READ-ONLY verifier running shell commands.
   • Verification steps as exact commands with expected outputs — the verifier runs nothing that mutates state.
   • Constraints capture what the builder must not touch or add.
4. Keep it under one page. A spec the verifier can't mechanically check is a bad spec.

Rules

• One spec = one coherent shippable change. Split anything larger.
• Never write acceptance criteria that require human judgment ("looks good") — only criteria a read-only agent can verify with commands and file inspection.
• Never edit a spec with status other than queued — running/shipped specs are records.