Loading...
Loading...
Found 21 Skills
Conduct an interactive discovery interview to produce a structured product specification. Triggers: write a spec, PRD, feature spec, requirements, product requirements, scope a project, brainstorm a feature, flesh out an idea, plan a new project. Uses AskUserQuestion for all user choices; WebSearch/WebFetch when the user wants research. Outputs: user stories, acceptance criteria, technical constraints, prioritized requirements in docs/specs/ per SPEC_TEMPLATE.md. Do NOT use for: implementation, code review, debugging, refactors, or when the user already has a complete spec they only want edited.
[Hyper] Create or update a ManyFast-style AI planning package from a rough product idea: PRD, visual planning diagram, feature spec, user flow, low-fidelity wireframe, HTML preview viewer, source log, and optional flow tracking under `.hypercore/prd/[slug]/`. Use when the user wants product planning output before implementation, especially PRD plus diagram/specs/flows/wireframes.
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.
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.
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.
Use when planning product roadmaps with Now/Next/Later horizons. Not for feature prioritization (use pm-prioritization).
Prioritization frameworks — RICE, WSJF, ICE, MoSCoW, and opportunity cost scoring for backlog ranking. Use when prioritizing features, comparing initiatives, justifying roadmap decisions, or evaluating trade-offs between competing work items.
This skill should be used when the user needs to structure what to build and when by converting discovery opportunities into prioritized bets and roadmaps. Use when organizing product capability blocks, writing solution briefs, planning quarterly cycles, or communicating product direction without false precision.