Best PromptsPlanning prompts
--- name: brainstorming description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation." --- # Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through nSKILL.md
Brainstorming Skill
The Superpowers entry gate: no implementation until a design exists, questions one at a time, 2-3 approaches, a committed spec, and user approval.
--- name: writing-plans description: Use when you have a spec or requirements for a multi-step task, before touching code --- # Writing Plans ## Overview Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch foSKILL.md
Writing Plans Skill
Write implementation plans for a skilled engineer with zero codebase context and questionable taste: bite-sized TDD tasks, exact files, no placeholders.
--- name: grilling description: Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. --- Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving depeSKILL.md
Grilling Skill
The interview primitive: one question at a time until shared understanding, a recommended answer each turn, facts looked up, decisions left to you.
--- name: to-spec description: Turn the current conversation into a spec and publish it to the project issue tracker, no interview, just synthesis of what you've already discussed. disable-model-invocation: true --- This skill takes the current conversation context and codebase understanding and produces a spec (you may know this documenSKILL.md
To-Spec Skill
Turn the current conversation into a PRD-style spec (no interview, pure synthesis) with user stories, implementation decisions, and agreed test seams.
--- name: to-tickets description: Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker; edges as text in one file per ticket locally, or native blocking links on a real tracker. disable-model-invocation: true --- # To Tickets Break a pSKILL.md
To-Tickets Skill
Break a spec into tracer-bullet tickets (complete vertical slices with explicit blocking edges) approved by you, then published to your tracker.
--- name: triage description: Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs. disable-model-invocation: true --- # Triage Move issues on the project issue tracker through a small state machine of triage roles. If this repo treats external pull requSKILL.md
Triage Skill
Move incoming issues and external PRs through a triage state machine: categorise, verify the claim by reproducing it, grill if needed, write agent-ready briefs.
--- name: wayfinder description: Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear. disable-model-invocation: true --- A loose idea has arrived, too big for one agent session, and wrapped in fSKILL.md
Wayfinder Skill
Plan work too big for one session as a shared map of decision tickets with a fog-of-war frontier: decisions, not deliverables, one per session.