plan

Plan by day

A plan is the only thing Nightshift reads. What this skill produces is read at 2 a.m. by a generator that cannot ask anyone anything, so every task must be complete on its own, and every open question must be closed before the plan merges. Announce: "Using nightshift:plan to turn this into a landable plan."

1. Size it, and stop early when you can

Size	Looks like	Do
Trivial	one sitting, one file or one clear edit, no design choice	No artifact. Say so and do it now, or hand it to the user.
Medium	a few files, one design choice or none, a day's work	A lean plan: header, constraints, tasks. No spec.
Large	several subsystems, choices that are hard to reverse, more than a day	A short spec first (docs/specs/YYYY-MM-DD-<slug>.md: problem, decision, what is out), user-approved, then the plan.

If the work spans independent subsystems, propose one plan per subsystem; each must produce working software on its own.

2. Settle the design, one question at a time

Read the code the change touches before asking anything. Then ask only what the code cannot answer, one question per turn, preferring multiple choice. State your interpretation and proceed when a wrong guess is cheap; ask when it is not. Two or three questions is typical; ten means the size was wrong.

HARD GATE: no implementation, no scaffolding, no "quick spike" before the user has approved the design (large) or the task list (medium). The loop lands what the plan says, so a plan written to a design nobody approved lands the wrong thing overnight.

3. Write the plan

Path: docs/plans/YYYY-MM-DD-<slug>.md (the repo's loop/config names the plan being landed; a plan directory elsewhere wins if the repo already has one).

# <Feature> Implementation Plan

**Goal:** one sentence.
**Architecture:** two or three sentences on the approach.
**Tech Stack:** what the tasks use.

## Global Constraints
- one line each: version floors, naming rules, platform requirements.
  Every task inherits these.

### Task 1: <component>

**Files:**
- Create: `exact/path.ts`
- Modify: `exact/existing.ts:120-140`
- Test: `tests/exact.test.ts`

**Interfaces:**
- Consumes: what this task uses from earlier tasks, exact names and types.
- Produces: what later tasks rely on, exact names and types.

- [ ] **Step 1:** write the failing test — show the test.
- [ ] **Step 2:** run it, expect FAIL with "<message>".
- [ ] **Step 3:** implement — show the code.
- [ ] **Step 4:** run `<the repo's test command>`, expect PASS.
- [ ] **Step 5:** commit: `git add <paths> && git commit -m "<why>"`.

## Open Questions
(must be empty before the plan merges)