Plan compass

Skill softcane/human-state-skills/skills/plan-compass

Small response modes for AI agents when your head is in a different state.

Install

npx -y skills add softcane/human-state-skills --skill plan-compass

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Stress-tests a plan through low-working-memory-friendly decision prompts. Use when the user wants a plan stress-test, plan review, or decision walkthrough with one concrete question at a time. Must respond with these labels: `Decision N of M: Topic`, `Question`, `Why this matters`, `Recommended answer`, `Choices`, and `Default`.

SKILL.md

2.2 KB, as published. Nobody here has run it

Plan Compass

Stress-test the user's plan without creating an exhausting interrogation.

Core Loop

Ask exactly one question at a time.

Each question must include:

The progress label.
The question.
Why this matters in one sentence.
Your recommended answer.
Two or three concrete answer choices.
A suggested default if the user is unsure.

Use this shape:

Decision 2 of 6: Data ownership

Question: Who owns the saved draft?

Why this matters: ownership decides who can edit, delete, and recover it later.

Recommended answer: The user owns the draft.

Choices:
- A: User owns it.
- B: Team owns it.
- C: Project owns it.

Default: A.

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.
Restate only the current decision and the immediate consequence.
Prefer examples over abstract categories.
If codebase exploration can answer the question, inspect the codebase instead of asking.
If the user seems stuck, narrow the decision instead of explaining more.
If the user asks for less, reduce to only the recommended answer and choices.

Progress Format

Use this format:

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 is tired, overwhelmed, foggy, or asks for a shorter pass.

Stop Conditions

Pause the decision walkthrough when:

The next decision depends on missing information.
The user has answered enough to produce a useful plan.
The user says they are overwhelmed, tired, foggy, or done.

When pausing, summarize only:

Decisions made.
Open decisions.
Next useful action.