Diagnose product premises and scope minimal viable starting points.
npx skills add https://github.com/garagon/nanostack --skill think-garagon
Please help me install this Agent Skill. Skill: think Source: https://github.com/garagon/nanostack/tree/main/think Command: npx skills add https://github.com/garagon/nanostack --skill think-garagon
It prevents building the wrong thing by applying strategic product thinking to validate premises, challenge scope, and surface the smallest starting point that delivers real value before planning or engineering work begins.
Type a short goal or problem to the agent, for example: /think Reduce onboarding dropoff by making the first task clearer.
High-intent search queries and answers about installing and using this skill.
To validate a product premise, strategic product thinking applies YC-grade diagnostics and six forcing questions to challenge assumptions and identify the smallest viable starting point. This prevents building the wrong feature by stress-testing scope before development begins.
Scoping a feature to a minimal viable wedge involves applying CEO cognitive patterns to determine the smallest starting point that delivers real value. The process outputs a concise Think Summary and a shareable markdown brief for immediate handoff.
Automated retrospective analysis for sprint planning evaluates sprint artifacts and git metrics to assess performance. It optionally initiates an autopilot mode to run an end-to-end sprint workflow when authorized, streamlining the development cycle.
Yes, you can use it for stress-testing a founder pitch. It runs a structured diagnostic to decide Founder, Startup, or Builder response intensity, ensuring premise validation and scope selection are appropriate for your specific context.
You do not need a pre-existing nanostack session workflow to generate a brief. The process creates an artifact compatible with the nanostack session workflow and writes a shareable markdown brief independently for handoff.
You should avoid automated premise validation when you lack a clear goal or problem statement to input. The diagnostic requires a defined objective to effectively apply forcing questions and challenge scope assumptions for product discovery.
jasonmeansGenerate structured Product Requirements Documents in markdown from user inputs.
YarikChekinReads sprint data from prd.json and progress.txt to generate dashboard and Claude Code kickoff prompt.
MichaelSolatiCompile and analyze sprint retrospective data from project artifacts into structured reports.
yocxy2Diagnose startup ideas using YC office hours methodology and generate design documentation.
