Convert product ideas into structured design doc outlines for scoping.
npx skills add https://github.com/JonOlsenCa/gstack-main --skill office-hours-jonolsenca
Please help me install this Agent Skill. Skill: office-hours Source: https://github.com/JonOlsenCa/gstack-main/tree/main/office-hours Command: npx skills add https://github.com/JonOlsenCa/gstack-main --skill office-hours-jonolsenca
Founders and engineers often struggle to translate an idea into a concrete plan before building. The YC Office Hours skill guides you through contextual gathering and design thinking to produce a clear, actionable design doc instead of jumping straight to code.
Describe your product idea to begin a YC office-hours session and receive a comprehensive design doc outline.
High-intent search queries and answers about installing and using this skill.
To turn a startup idea into a design doc, provide your product concept and project context for guided synthesis. The session applies design thinking to define clear problems, target users, and scope boundaries before any code is written.
The best way to scope a side project is running a consultative design review to validate assumptions and tradeoffs. This yields a design doc specifying audience, scope boundaries, success metrics, and constraints to guide later decision-making.
Yes, design thinking can define product requirements for an open-source initiative. The session gathers contextual inputs to specify constraints, success metrics, and scope boundaries tailored to your project context.
You create a design doc outline for stakeholder alignment by describing your product idea to start a guided session. It tailors the workflow using Startup or Builder modes to produce structured sections for scope, risks, and outcomes.
You need a design doc for product management planning when translating an idea into a concrete plan before building. It helps founders and engineers avoid jumping straight to code by defining clear problems, users, and scope boundaries.
Yes, the office-hours skill validates startup assumptions through a collaborative consultative review session. It distinguishes between Startup and Builder modes to tailor routing decisions and validate tradeoffs for your project context.
concept2cureGenerate structured design docs with goals, scope, risks, and milestones.
yashs33244Review engineering architecture and execution plans for implementation risks.
yohayetsionCreate, update, and retrieve roadmap items with scope and dependencies.
lengoctuong2005Generate interactive HTML mockups for UI/UX design comparison.
