Loading...
Loading...
Found 252 Skills
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.
Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.
Use when starting a Beat change to create spec artifacts — not for task breakdown, implementation, or exploration
Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.
Vendor-neutral skill to generate a release risk checklist from scope, dependencies, and rollout constraints.
Visualize and optimize workflow with Kanban boards. Use when managing team work, identifying bottlenecks, improving delivery flow, or implementing continuous improvement in product development.
Collaborative planning using abstract roles (designer + inspiration + reviewer).
Linear API for issue tracking. Use when user mentions "Linear", "linear.app", shares a Linear link, "~ENG-123", "create issue", or asks about Linear tasks.
Use when modifying an existing em plan or task files. Triggers on: "update em", "change plan", "modify epic", "add task", "remove task", "rename phase", "apply annotations", "edit plan". Applies inline > and >> annotations or accepts conversational changes to plan.md or task milestone files.
Discuss phase details and approach
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.