plan-compass

Name: plan-compass
Author: softcane

63stars2forks

How to install plan-compass?

softcane/human-state-skills/plan-compass

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

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Plan Compass
2
3	Stress-test the user's plan without creating an exhausting interrogation.
4
5	## Core Loop
6
7	Ask exactly one question at a time.
8
9	Each question must include:
10
11	1. The progress label.
12	2. The question.
13	3. Why this matters in one sentence.
14	4. Your recommended answer.
15	5. Two or three concrete answer choices.
16	6. A suggested default if the user is unsure.
17
18	Use this shape:
19
20	```text
21	Decision 2 of 6: Data ownership
22
23	Question: Who owns the saved draft?
24
25	Why this matters: ownership decides who can edit, delete, and recover it later.
26
27	Recommended answer: The user owns the draft.
28
29	Choices:
30	- A: User owns it.
31	- B: Team owns it.
32	- C: Project owns it.
33
34	Default: A.
35	```
36
37	## Interaction Rules
38
39	- Do not call the process "grilling" unless the user uses that word first.
40	- Keep questions short and specific.
41	- Do not ask broad open-ended questions unless unavoidable.
42	- Do not ask multiple questions in one response.
43	- Do not require the user to hold previous answers in memory.
44	- Restate only the current decision and the immediate consequence.
45	- Prefer examples over abstract categories.
46	- If codebase exploration can answer the question, inspect the codebase instead
47	of asking.
48	- If the user seems stuck, narrow the decision instead of explaining more.
49	- If the user asks for less, reduce to only the recommended answer and choices.
50
51	## Progress Format
52
53	Use this format:
54
55	```text
56	Decision 2 of 6: Data ownership
57	```
58
59	Choose the total decision count conservatively. Prefer 4 to 6 decisions for a
60	normal plan. Use fewer when the user is tired, overwhelmed, foggy, or asks for a
61	shorter pass.
62
63	## Stop Conditions
64
65	Pause the decision walkthrough when:
66
67	- The next decision depends on missing information.
68	- The user has answered enough to produce a useful plan.
69	- The user says they are overwhelmed, tired, foggy, or done.
70
71	When pausing, summarize only:
72
73	- Decisions made.
74	- Open decisions.
75	- Next useful action.

People who liked this also viewed

6 picks

Type

plan-compass

63stars2forks

View on GitHub

How to install plan-compass?

softcane/human-state-skills/plan-compass

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Plan Compass
2
3	Stress-test the user's plan without creating an exhausting interrogation.
4
5	## Core Loop
6
7	Ask exactly one question at a time.
8
9	Each question must include:
10
11	1. The progress label.
12	2. The question.
13	3. Why this matters in one sentence.
14	4. Your recommended answer.
15	5. Two or three concrete answer choices.
16	6. A suggested default if the user is unsure.
17
18	Use this shape:
19
20	```text
21	Decision 2 of 6: Data ownership
22
23	Question: Who owns the saved draft?
24
25	Why this matters: ownership decides who can edit, delete, and recover it later.
26
27	Recommended answer: The user owns the draft.
28
29	Choices:
30	- A: User owns it.
31	- B: Team owns it.
32	- C: Project owns it.
33
34	Default: A.
35	```
36
37	## Interaction Rules
38
39	- Do not call the process "grilling" unless the user uses that word first.
40	- Keep questions short and specific.
41	- Do not ask broad open-ended questions unless unavoidable.
42	- Do not ask multiple questions in one response.
43	- Do not require the user to hold previous answers in memory.
44	- Restate only the current decision and the immediate consequence.
45	- Prefer examples over abstract categories.
46	- If codebase exploration can answer the question, inspect the codebase instead
47	of asking.
48	- If the user seems stuck, narrow the decision instead of explaining more.
49	- If the user asks for less, reduce to only the recommended answer and choices.
50
51	## Progress Format
52
53	Use this format:
54
55	```text
56	Decision 2 of 6: Data ownership
57	```
58
59	Choose the total decision count conservatively. Prefer 4 to 6 decisions for a
60	normal plan. Use fewer when the user is tired, overwhelmed, foggy, or asks for a
61	shorter pass.
62
63	## Stop Conditions
64
65	Pause the decision walkthrough when:
66
67	- The next decision depends on missing information.
68	- The user has answered enough to produce a useful plan.
69	- The user says they are overwhelmed, tired, foggy, or done.
70
71	When pausing, summarize only:
72
73	- Decisions made.
74	- Open decisions.
75	- Next useful action.

People who liked this also viewed

6 picks

Type