plan-compass
From the author
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`.
Install
npx skills add softcane/human-state-skills --skill plan-compass -a claude-code
Installs to .claude/skills/plan-compass/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 81
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- plan-interrogaterohitg00/pro-workflowStress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.Planning★ 2.9K
- personal-boardroomFAIRY123456789/human-edge-agent-skillsStress-test a difficult career, startup, study, money, product, or life decision through a small board of explicit decision lenses, then synthesize one evidence-weighted recommendation. Use when the user is torn between options, has several identities or goals in conflict, keeps receiving contradictory advice, or wants more than a generic trade-off list.Testing★ 100
- challengepedrohcgs/claude-code-my-workflowStress-test a finding against the choices you did not make. Enumerates the discrete forks a competent analyst could have taken (measure definition, sample filter, control set, clustering level, weighting, functional form), runs the specification grid, and reports the distribution rather than a point estimate — then attacks the identifying assumption with named, computable sensitivity statistics. Use when the user says "is this robust", "challenge this result", "specification curve", "multiverse", "how sensitive is this", "what if I'd used a different measure", "stress-test my estimate", or before a result becomes a headline claim. NOT a reviewer of prose or code — it challenges the CLAIM.Testing★ 1.7K
- ceo-advisorcbrock84/headcountPressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.Testing★ 2.1K
- test-planningpetrkindlmann/qa-skillsBuild a single sprint or release test plan. Covers feature decomposition into testable scenarios, requirements-to-test coverage mapping, effort estimation by test type, prioritization matrices (risk × effort), resource allocation, and scheduling with buffers. Use when: "sprint test plan," "release test plan," "what to test this sprint," "test estimation," "coverage mapping." Not for: multi-quarter strategy — use `test-strategy`. Not for: ranking areas by risk — use `risk-based-testing`. Not for: the go/no-go decision itself — use `release-readiness`. Related: test-strategy, risk-based-testing, release-readiness.Testing★ 209
- red-teamsuboss87/FDEOpsStress-test a plan, brief or delivery claim against evidence and plausible failure modes. Use when the user asks for a red team or preparation for a consequential decision.Testing★ 940
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in