Loading...
Loading...
Found 66 Skills
Create critical MVP application briefs through ruthless scope-cutting dialogue. Use when user wants to turn business ideas and processes into applications. Ruthlessly cuts scope, challenges overengineering, and focuses on minimum viable product to test hypotheses. Creates structured MVP briefs in .ideas/[name]/app.md. Triggers include "build an app", "MVP for this", "what should the application do", or readiness to design application.
Senior Product Manager responsible for the end-to-end product development process from requirements analysis to product design. Use this when you need support with: (1) Requirements analysis and product direction, (2) User personas and scenario analysis, (3) Feature and interaction design, (4) PRD writing, (5) Feasibility assessment. Trigger words: product design, requirements analysis, user persona, PRD, feature planning, MVP, user story, product solution.
Help users break down product requirements into phased version plans. Triggered when users say "split versions", "version planning", "how to build MVP", "phased implementation".
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", or "test assumptions". Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done. Trigger with 'lean', 'startup'.
Apply Lean Startup methodology — Build-Measure-Learn loop, MVP, validated learning, and pivot decisions. Use this skill when the user is launching a new product or startup and needs to validate ideas quickly, design an MVP, decide whether to pivot or persevere, or reduce wasted effort on unvalidated assumptions — even if they say 'should we build this', 'how do we test this idea', 'when should we pivot', or 'we're burning cash with no traction'.
Prevent feature creep when building software, apps, and AI-powered products. Use this skill when planning features, reviewing scope, building MVPs, managing backlogs, or when a user says "just one more feature." Helps developers and AI agents stay focused, ship faster, and avoid bloated products.
Guides Claude from idea to working prototype using frameworks from OpenAI, Figma, and Airbnb. Use when starting new product features, planning MVP scope, making build-vs-buy decisions, or guiding users from concept to shippable prototype. Applies AI-first thinking (Kevin Weil), simplicity forcing functions (Dylan Field), and complete experience design (Brian Chesky).
Cut scope ruthlessly using Shape Up's appetite-first approach. Use when asked to reduce scope, find the MVP, trim features, ship faster, or figure out what to cut. Applies fixed time variable scope thinking and scope hammering techniques.
Use when a founder has a rough product idea and wants autonomous deep validation, market and competitor research, and an evidence-based MVP decision with minimal back-and-forth.
Propose concrete, high-leverage product/UX improvements to increase a software project's appeal and retention. Use when asked to generate product improvement proposals, UX ideas, onboarding/doc improvements, packaging/pricing positioning suggestions grounded in repo evidence, and prioritized MVP plans (ideation only; no implementation).
Validate Business Requirements Documents (BRD) against Layer 1 MVP schema standards
End-to-end workflow for taking a new tool idea from research to working MVP. Use when the user has an idea for a CLI tool, library, or small project and wants to go from concept to initial implementation. Triggers on "I have an idea for a tool", "build a new CLI", "create a new project", "kickoff new tool", "I want to build", "let's build a new", "新しいツールを作りたい", "CLIを作る".