تشغيل أي مهارة في Manus بنقرة واحدة

plan-compass

النجوم٦٢

التفرعات٢

آخر تحديث٢٤ مايو ٢٠٢٦ في ٠٧:٢٩

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`.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

softcane

softcane/human-state-skills

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

متخصصو إدارة المشاريعمهن الأعمال والعمليات المالية·SOC 13-1082

SKILL.md

readonly

name	plan-compass
description	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`.

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.

المزيد من هذا المستودع

نفس المستودع

brain-fog-mode

softcane/human-state-skills

Use when the user asks for brain fog mode or describes low working memory, fatigue, sleep debt, illness, recovery, or difficulty thinking clearly. Use Current state, Next action, Do not do yet, and Stop point by default. If the user explicitly asks for only the next step, output only Next action. Next action is exactly one tiny action only, with no setup-plus-sending and no then/after/once follow-up. Current state may include one or two short context sentences unless this is a Next-action-only response. For concrete task prompts, choose the earliest visible unit of progress and stop. Before final, rewrite if Next action hides a sequence or if Stop point does not start with "Stop when".

2026-06-0462

foggy-mode

softcane/human-state-skills

Use when the user has low working memory, brain fog, fatigue, sleep debt, illness, recovery state, or cognitive depletion. Final answer must contain only Current state, Next action, Do not do yet, and Stop point. Current state may include one or two short context sentences. Next action is exactly one action: one placement, one opening, one sentence, or one message. Never combine setup plus sending. For concrete multi-step tasks, choose the earliest visible next unit. Before final, rewrite if Next action hides a sequence or if Stop point does not start with "Stop when".

2026-06-0462

burnout-mode

softcane/human-state-skills

True alias for overloaded-mode. Use when the user asks for burnout mode or describes burnout-like overload, exhaustion, freezing, overcommitment, or inability to choose what matters. Must use exact labels Do this first, Send/say this, Do now, Defer, Drop, Minimum viable version, and Next action. Do now is 1-3 top-level bullets only. Next action is exactly one atomic immediate action; no then/after/once/and-combined actions. Brief context is allowed inside existing labels when it lowers uncertainty without adding work. For avoidance prompts, prefer one honest update as the next action.

2026-06-0462

overloaded-mode

softcane/human-state-skills

Use when the user is overwhelmed, frozen, overcommitted, burnout-adjacent, or unable to decide what matters. Must use exact labels Do this first, Send/say this, Do now, Defer, Drop, Minimum viable version, and Next action. Do now is 1-3 top-level bullets only. Next action is exactly one atomic immediate action; no then/after/once, no combined actions, no item 4, nested list, or runbook. Brief context is allowed inside existing labels when it lowers uncertainty without adding work. Do this first must not be blank. Always include Drop. Put investigation, cleanup, catch-up, and follow-up checks under Defer unless they are the single urgent priority.

2026-06-0462

reality-check-mode

softcane/human-state-skills

Use for grounding, anti-sycophancy, reality checking, or AI-loop escalation when the user asks to interpret ordinary artifacts as hidden, personal, mystical, threatening, or specially meaningful signals. For hidden-meaning prompts, What I can say must be exactly: stress and repetition can make ordinary patterns feel personally meaningful. Use only Grounding, What I can say, and Safer next step. Do not decode hidden meanings in numbers, repeated phrases, model wording, coincidences, dreams, posts, tool output, timing, or everyday events. For repeated symbols, What I can say must be exactly: fear can make patterns feel personally meaningful. For AI-bond prompts, What I can say must be exactly: emotionally loaded coincidences can feel meaningful without being evidence of a bond. Safer next step should usually be exactly send one message to a trusted real person. No bullets, numbered lists, message drafts, or pattern analysis.

2026-06-0462

normal-mode

softcane/human-state-skills

Use when the user wants to stop any active human-state response mode and return to the assistant's normal response style. Do not announce "Normal mode active" or add a mode-status preface; just answer normally.

2026-06-0462

name	plan-compass
description	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`.

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.