scaffold

Ops Scaffold

Set up a new non-code project management repo, or adjust an existing one to match the ops conventions.

Detect Mode

Check the current directory:

• If CLAUDE.md exists → Adjust mode: read it, compare against the template below, and propose specific changes. Don't overwrite — use Edit to patch. Ask before creating missing folders.
• If no CLAUDE.md → New repo mode: run the full interview and scaffold from scratch.

Interview (New Repo Mode)

Ask the user:

1. Project name — what the project is called
2. One-paragraph description — what the project does, who it's for
3. Constraints — team size, budget, timeline, key limitations
4. The charter — one topic at a time, offering your best guess from what they've said, and reading each answer back before you write it: who the project is for and the job they need done; 2-4 goals for the near term, each with how they'd know it is working; the audiences those goals target beyond the people it's for (a funder, a partner, a would-be maintainer); non-goals; what they care about and won't trade away; how bold to be. These become charter.md
5. Initial domain areas — what topics will the project cover? These become the initial subfolders. Examples:
   • Marketing, legal, fundraising, partnerships, technical research
   • Or more specific: grants, audience growth, competitor analysis
6. Connected to a coding repo? — ask if this ops repo is paired with a codebase. If yes, ask for the relative path from this repo to the code repo root (e.g., ../ if sibling directories, ../app/ if nested). This enables read-only access to the code for context.

Interview (Adjust Mode)

Read the existing structure (CLAUDE.md, MEMORY.md, folder listing). Then ask:

1. What needs changing? — or just check against the template and propose fixes
2. Missing folders? — offer to create any missing standard folders with INDEX.md files
3. CLAUDE.md drift? — show specific differences from the template and offer to patch. An ## Autopilot section, which autopilot's setup writes, is not drift: leave it as it is. An autopilot/ folder is autopilot's memory from before it moved into this layout: leave it, and suggest running autopilot in a session started from the code repo, which moves it
4. No charter.md? — a repo set up before it existed keeps its goals in MEMORY.md, under "Constraints & Goals". Offer to move them into a new charter.md (template below), asking for what the template needs and MEMORY.md doesn't say, and to leave the constraints in MEMORY.md with the pointer line from its template. Where an autopilot/ folder exists, leave this to autopilot's move, which merges its own charter in