Loading...
Loading...
Found 455 Skills
Use before building anything new or when a plan needs review. Not for bug fixes or small edits.
Clarify or discuss a proposed task, plan, design update, or ADR by resolving the highest-value unresolved decisions, decision criteria, trade-offs, and option boundaries until the inputs are ready for task creation, task planning, task/design updates, ADR writing, or safe implementation continuation. Use this as the default path when the user asks to clarify, discuss criteria, compare options, stress-test a design, or otherwise resolve material unresolved questions before proceeding. When clarification ends, resume the invoking workflow. It may also be used for general grilling when explicitly selected or when no other default grilling skill is available.
Convert markdown planning documents to Overseer tasks via MCP codemode. Use when converting plans, specs, or design docs to trackable task hierarchies.
Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, leadership, customer-facing, mixed). Surfaces a primary CTA up front, flags technical-to-business translations for user verification, and detects thread continuation from prior updates.
Day 2 morning move of a Foundation Sprint. Forces generation of 3 to 7 candidate approaches as one-page summaries before the team converges on a top bet. Use after Day 1 is signed and before Magic Lenses on Day 2 afternoon. Enforces a minimum of 3 approaches to prevent first-idea anchoring. Each approach summary names what it is, why it serves the differentiators, and includes a simple visual.
Associate two tasks (cross-project support)
Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
Extract actionable Linear tickets from ambiguous input — Slack conversations, call transcripts, screenshots, meeting notes, or any unstructured material. Proposes tickets in a scratchpad file for user review, then creates them in Linear on approval. Use when the user wants to turn conversations, transcripts, screenshots, or notes into Linear tickets. Also use when user says "create tickets from this", "send to linear", "make issues from this call/chat", or provides raw material and asks for tickets.
PRD review, requirements review, check PRD quality. Use when: Review is required after PRD completion, "review PRD", "PRD review", "requirements review"
Create comprehensive, self-contained task prompts for implementing features or fixing bugs.
Use after PR hardening is complete, to sync knowledge across global documents and prepare the next phase
Break requirements into epics and user stories. Use when the user says "create the epics and stories list"