Cursor plugin specification and official plugins
TypeScript
feat(pstack): add /sharpen (#615)
lauren79afd75d5bd5
diff --git a/pstack/README.md b/pstack/README.mdindex 6314039f..dbbef9bc 100644--- a/pstack/README.md+++ b/pstack/README.md@@ -114,6 +114,7 @@ to keep [`/poteto-mode`](./skills/poteto-mode/SKILL.md) on across turns, pick it| [`/poteto-mode`](./skills/poteto-mode/SKILL.md) | default entry point for any non-trivial task. || [`/poteto-help`](./skills/poteto-help/SKILL.md) | you're new to pstack, or unsure which skill, playbook, or principle fits. finds out what you're trying to do, answers that part, and hands you a prompt to type. runs only when you type `/poteto-help`. || [`/in-your-own-words`](./skills/in-your-own-words/SKILL.md) | you want the agent to play back your goal and the problem before it starts. runs only when you type `/in-your-own-words`. |+| [`/sharpen`](./skills/sharpen/SKILL.md) | you want a task approached the way a top expert would, aimed at what you're really after, without overspecifying it or deciding your choices for you. || [`/how`](./skills/how/SKILL.md) | you want a walkthrough of how a subsystem works. || [`/why`](./skills/why/SKILL.md) | you want to know why something was built this way. discovers available MCPs at run time and queries each evidence category in parallel (source control, issue tracker, long-form docs, real-time chat, infra observability, error tracking, analytics warehouse). || [`/recall`](./skills/recall/SKILL.md) | you're starting or resuming work and want your recent context on a topic rebuilt from your own chat history and the shared record, handed back as a tight current-state brief. |diff --git a/pstack/skills/poteto-help/SKILL.md b/pstack/skills/poteto-help/SKILL.mdindex cbe18c83..dc443648 100644--- a/pstack/skills/poteto-help/SKILL.md+++ b/pstack/skills/poteto-help/SKILL.md@@ -64,6 +64,7 @@ The default answer is `/poteto-mode`, which runs most of the others when its ste|---|---|| Do any non-trivial task with rigor | [`/poteto-mode`](../poteto-mode/SKILL.md) || Check that the agent understood their goal and the problem before it starts | [`/in-your-own-words`](../in-your-own-words/SKILL.md) |+| Aim a task higher before starting: more expert, more outcome-focused, not overspecified | [`/sharpen`](../sharpen/SKILL.md) || Know how code works now, or where new code should live | [`/how`](../how/SKILL.md) || Know why code is shaped this way, or where a number came from | [`/why`](../why/SKILL.md) || Understand a change or subsystem, explained plainly | [`/teach`](../teach/SKILL.md) |diff --git a/pstack/skills/poteto-help/references/recipes.md b/pstack/skills/poteto-help/references/recipes.mdindex a78942c7..d13da3a0 100644--- a/pstack/skills/poteto-help/references/recipes.md+++ b/pstack/skills/poteto-help/references/recipes.md@@ -6,6 +6,7 @@ Swap in the real paths, skills, and done checks. Informal wording works.- `/poteto-mode read <thread>. restate the underlying issue in your own words, in plain english.`- `/in-your-own-words <long or messy ask>`+- `/sharpen <your task>`- `/poteto-mode investigate why <symptom>. give me what we know, what data you used, and your best hypotheses. don't change any code yet.`- `use /how to understand <subsystem>. then use /why to find out why it broke recently.`- `/recall my work on <topic> from last week, then read <issue>.`diff --git a/pstack/skills/sharpen/SKILL.md b/pstack/skills/sharpen/SKILL.mdnew file mode 100644index 00000000..4f9bb4ab--- /dev/null+++ b/pstack/skills/sharpen/SKILL.md@@ -0,0 +1,7 @@+---+name: sharpen+description: "Sharpen a task before starting: the expert approach, what the user is really after, and the right level of specification. Use for /sharpen."+disable-model-invocation: true+---++Before starting, ask how a top expert would approach this task (their raw sources, their real methods, an outside check that the result is right), what the user is really after, and whether the task is over- or underspecified. Loosen constraints that don't serve the goal as readily as you add ones that do, and leave choices that are the user's to make open instead of deciding them. Fold in only what makes the work better, not bigger, but always keep one outside check that the result is right, without narrating the framing, then do the work. Don't hand back a rewritten prompt.