skill-softcane-human-state-skills-plan-compass · by Install
$ agentstack add skill-softcane-human-state-skills-plan-compass ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-softcane-human-state-skills-plan-compass) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 ownershipChoose 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: softcane
- Source: softcane/human-state-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.