plan-compass
/plan-compass
Stress-tests a plan through dependency-aware, easy-to-answer decision prompts. Use when the user wants a plan stress-test, plan review, or decision walkthrough with one concrete question at a time. During decision questions, use these labels: `Decision N of M: Topic`, `State`, `Question`, `Recommendation/default`, `Why this matters`, and `Choices`.
- Author
- softcane ↗
- Repository
- human-state-skills ↗
- Licence
- MIT
- Last repository change
- 03.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Stress-tests a plan through dependency-aware, easy-to-answer decision prompts. Use when the user wants a plan stress-test, plan review, or decision walkthrough with one concrete question at a time. During decision questions, use these labels: `Decision N of M: Topic`, `State`, `Question`, `Recommendation/default`, `Why this matters`, and `Choices`.
Original author description
Stress-tests a plan through dependency-aware, easy-to-answer decision prompts. Use when the user wants a plan stress-test, plan review, or decision walkthrough with one concrete question at a time. During decision questions, use these labels: `Decision N of M: Topic`, `State`, `Question`, `Recommendation/default`, `Why this matters`, and `Choices`.
How it works
- Core Loop
- Interaction Rules
- Progress Format
- Undecided Sweep
- Confirmation Gate
- Stop Conditions
SKILL.md preview
--- name: plan-compass description: >- Stress-tests a plan through dependency-aware, easy-to-answer decision prompts. Use when the user wants a plan stress-test, plan review, or decision walkthrough with one concrete question at a time. During decision questions, use these labels: `Decision N of M: Topic`, `State`, `Question`, `Recommendation/default`, `Why this matters`, and `Choices`. --- # 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 the line grow. - Prefer examples over abstract categories. - If the user cannot choose, narrow the decision instead of explaining more. - If you lack the facts to recommend, say so in `Recommendation/default` and name the one fact that would decide it in `Why this matters`. - If the user asks for less, output only `Recommendation/default` and `Choices`. This is an explicit exception to the normal question format. - Keep tangents in a private parking lot. Finish the current branch first and surface a parked item only when it becomes the next dependency. - Make progress visible without praise or gamification. ## Progress Format Use this format: ```text Decision 2 of 6: Data ownership ``` Choose the total decision count conservatively. Prefer 4 to 6 decisions for a normal plan. Use fewer when the user asks for a shorter pass. If an answer adds or removes a branch, update the total openly; do not preserve a false count. ## Undecided Sweep Run this sweep before every ending, whether the walkthrough reaches the confirmation gate or pauses. Check silently whether the plan decides four things: what happens when it fails, who is allowed to do it, how you undo it, and how you know it worked. List any that are undecided under `Open`. Do not turn the sweep into extra questions. ## Confirmation Gate When the decisions are sufficient, run the undecided sweep, stop asking decision questions, and show only: - `Plan ready for confirmation` - `Decisions locked`: the agreed decisions in no more than five bullets. - `Open`: unresolved decisions, including ones the sweep found but nobody asked. Use `None` only when the sweep found nothing. - `Next action`: exactly one small, atomic next action. - `Confirmation`: ask the user to approve the summary or name one change. This confirmation response replaces the decision labels and is an explicit exception to the question format. Do not act on the plan until the user confirms the shared-understanding summary. After confirmation, act only if the user requested implementation; otherwise hand off the confirmed plan and next action. ## Stop Conditions Pause the decision walkthrough when: - The next decision depends on missing information. - The user asks to pause, stop, or end the walkthrough. When pausing, run the undecided sweep and summarize only: - Decisions made. - Open decisions, including ones the sweep found but nobody asked. Use `None` only when the sweep found nothing. - One small, atomic next action. Do not request confirmation while required information is missing or when the user asks to pause. Preserve the state so the next turn can resume from one decision.
Versions
The database has no other skills named plan-compass.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 342da8b074b7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90decision
Structure a decision as one or two multiple-choice questions at a time, with tradeoffs and a recommendation for every question. Use when the user wants guided help choosing among alternatives or explicitly asks for a decision session. - 86grill-me
Run a relentless interview of the user about a plan, design, or change — depth-first, one question at a time, each question carrying a recommended answer and code-checked before it is asked — until every branch of the decision tree is resolved. Use before any non-trivial change,… - 90core-grilling
Use only when the user explicitly invokes this skill to stress-test an existing plan or design through one load-bearing question at a time. - 87grill-me
Stress-test a plan, decision, or design through dependency-ordered questions and recommended answers. Use when the user asks to be grilled or wants assumptions challenged before implementation. - 100compass
Read or update the per-repo arc-state file (docs/compass.md). Tracks current arc, last meaningful commit, open loops, next move, and don't-forget items. Auto-maintained by build, merge-pr, finish; read by getting-started. Use "compass read" to inspect project state, "compass… - 100workflow-grilling
Interview the user about a plan, decision, or idea one question at a time until you agree. Use when "grill me", "stress-test this plan", "interview me about this", "poke holes in this", "challenge my thinking", or before a non-trivial design.