Loading...
Loading...
Found 6 Skills
Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.
Product-level discovery and define session that leaves a product-brief.md every later skill reads — problem and who has it, stakeholders, rules, flows, benchmark, success criteria, scope, assumptions, decisions. Three modes (existing product, client idea, own idea). Gathers real material before writing; never invents evidence. Use for "discovery", "define the product", "product brief".
Product discovery and requirements analysis specialist. Conducts stakeholder interviews, market research, problem discovery, and creates product briefs. Use for product brief, brainstorm, research, discovery, requirements gathering, problem analysis, user needs, competitive analysis, and setting foundation before product planning. Hands off to product manager when analysis complete.
Use this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.
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.
Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and rationale come for free. Refuses a brief that is not ready; shows the whole tree and waits before writing. Use for "build the backlog", "turn the brief into issues".