Loading...
Loading...
Found 10 Skills
Help users scope projects and cut features effectively. Use when someone is defining an MVP, dealing with scope creep, trying to ship faster, or needs to make tradeoffs about what to build.
Create a visionary press release following Amazon's "Working Backwards" methodology to define and communicate a product or feature before building it. Use this to align stakeholders on the customer va
Generate user demand research reports from real user feedback. Scrape and analyze feature requests, complaints, and questions from Reddit, X, and GitHub.
Help users prioritize product roadmaps and backlogs. Use when someone is deciding what to build next, sequencing features, allocating resources across projects, handling stakeholder requests, or struggling with too many competing priorities.
Create an Amazon-style PR/FAQ (future press release + FAQ) plus a backcasting launch plan to align on customer value, scope, and GTM readiness. Use for working backwards, PRFAQ / PR-FAQ, future press release, backcasting, launch plan.
Design and analyze business models using the Business Model Canvas framework. Use when evaluating startups, planning new products, pivoting existing businesses, or understanding how companies create and capture value.
End-to-end product development for iOS/macOS apps. Covers market research, competitive analysis, PRD generation, architecture specs, UX design, implementation guides, testing, and App Store release. Use for product planning, validation, or generating specification documents.
Write or update a single-feature PRD (`Type: feat`/`fix`/`chore`) with scope, user stories, and acceptance criteria. Triggers: plan prd, write feature spec, define acceptance criteria, update prd.
Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.
Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.