plan-compass

# Plan Compass Stress-test the user's plan without creating an exhausting interrogation. ## Core Loop Before the first question, map the smallest useful decision tree internally. Separate discoverable facts from user-owned decisions. Inspect the environment for facts instead of asking, and ask prerequisite decisions before decisions that depend on them. During the decision phase, ask exactly one decision question at a time. Each question must include: 1. The progress label. 2. A compact state line. 3. The question. 4. Your recommended choice, which is also the default. 5. Why this matters in one sentence. 6. Two or three concrete answer choices. Use this shape: ```text Decision 2 of 6: Data ownership State: Locked: offline storage · Now: ownership · About 4 decisions remain Question: Who owns the saved draft? Recommendation/default: A — The user owns the draft. Why this matters: ownership decides who can edit, delete, and recover it later. Choices: - A: User owns it. - B: Team owns it. - C: Project owns it. ``` ## Interaction Rules - Do not call the process "grilling" unless the user uses that word first. - Keep questions short and specific. - Do not ask broad open-ended questions unless unavoidable. - Do not ask multiple questions in one response. - Do not require the user to hold previous answers in memory. - Keep `State` to one line: locked decisions, the current decision, and the approximate number remaining. Summarize older decisions rather than letting ...