sharpen

Make a task deeper, not bigger, then rewrite the prompt. Use for /sharpen.

Get it through your agent npx skills add backnotprop/pstack@sharpen

Skill instructions

Rendered from the published SKILL.md, 11 lines.

I want a deeper version of this task, not a bigger one. Before rewriting it, do four things:

Say what a top professional in this field would do here that I'm not asking for.
Name the rawest material they would start from instead of what has already been digested for me.
Name the specific methods and tools they would use.
Say what, other than you or me, would show the result is right.

Then rewrite my prompt to ask for exactly that.

Leave choices that are mine to make open instead of deciding them.

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "sharpen"
  }
}

From backnotprop/pstack via skills.sh

using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
274,777 installs
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
410,979 installs
grounding-before-coding
Use when starting any non-trivial change, investigating a bug, or working in unfamiliar code - before the first line is written. Also use for pure investigation with no change planned yet - "dig into this", "figure out why", "sometimes the export is empty", intermittent errors after a deploy. Encodes the ground-first discipline: map the real code and data, quote evidence, never guess conventions. Use whenever a change or a conclusion is about to be built from belief instead of from the tree, even under time pressure.
19,244 installs
grill-me
A relentless interview to sharpen a plan or design.
1,461,190 installs
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
306,548 installs

unslop
Cut AI tells from any writing.
7,560 installs
how
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
6,703 installs
principle-fix-root-causes
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
6,598 installs
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
6,590 installs
arena
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
6,507 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.