Folder in, plan out

A project is a folder you point the extension at. Everything the room produces lands next to your code, in plain Markdown you can read and commit.

Folder as project

Open a git workspace and load it as the project. Nothing is copied into a cloud workspace and nothing is indexed off-machine — the Indexer reads the repo in place, through the same file APIs the editor uses.

What gets written

• PLAN.md — the living plan. Required sections: Goal, Scope, Milestones (with acceptance criteria per milestone), Risks, and per-role Roles.
• EXECUTION.md — emitted by /freeze. The ordered manifest you chair the Drafter through.
• memory/ — audit trail, session handoff, and validation reports. Append-only.

Freezing a plan

/freeze is a gate, not a formality. It refuses with PlanIncomplete if a required section is missing, and refuses while any BLOCKER raise is still open. The error names the missing piece, so the fix is mechanical.

A frozen plan is the handoff artifact. If you stop working for a week, EXECUTION.md plus the trail in memory/ is enough to resume without re-deriving the argument.

Proving it works on your stack

Run the concept test once on something small — about fifty lines of a feature you actually want. Seat three models from three providers, start in brainstorm, describe the feature in a paragraph, and watch for two signals: did a read-only seat raise something the Drafter missed, and did admitting it change PLAN.md? If both fire once, the concept holds for you.