product-loop
SolidDiscovery, specification, launch, and learning for a product in one loop. Build-or-stop calls, MVP wedges, demand tests, customer interviews, PRDs, requirements, user journeys, acceptance, positioning, onboarding, rollout, pricing, pivots.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- fmind
- Repository
- fmind/dotfiles
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- Go
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
growth-loops
Design growth loops (Reforge/Balfour framework). Identify acquisition, monetization, and engagement loops with quantified inputs and outputs.
product-discovery
Apply how high-performing product teams work — continuous discovery, opportunity-solution trees, Amazon working-backwards / PR-FAQ specs, prioritization (RICE/ICE/MoSCoW/Kano/WSJF), goal-setting (OKRs, North Star, HEART, AARRR), outcome-based roadmaps, JTBD + usability testing + MVP, Cagan's four risks, empowered teams, and accessibility as a product duty. Use during discovery, PRD/brainstorm, prioritization, roadmapping, defining success metrics, validating an idea, or any change request — i.e. Stages 0/1/9 and whenever deciding WHAT to build and why.
product-discovery
This skill should be used when the user has a product idea but is not sure what to build, what the MVP is, or where to start. Trigger phrases include "I have an idea for a product", "not sure what to build", "what should the MVP be", "where do I start", "is this idea any good", "help me scope this", "I want to build something but". Inspired by Design Sprint and Lean Startup. It separates the problem from the solution, validates the market, and defines a prioritized MVP.