Generate a YC-style product design document through structured questioning.
npx skills add https://github.com/bhianerd/aimemory --skill office-hours-bhianerd
Please help me install this Agent Skill. Skill: office-hours Source: https://github.com/bhianerd/aimemory/tree/main/.claude/skills/gstack/office-hours Command: npx skills add https://github.com/bhianerd/aimemory --skill office-hours-bhianerd
Office-hours helps you understand a product idea deeply before you build, by forcing clear demand, status quo, specific users, and a narrow wedge so you can write a high-signal design doc instead of drifting into code-first guessing.
Use /office-hours and describe your product idea or the thing you’re trying to think through, and ask it to produce a design doc for you.
High-intent search queries and answers about installing and using this skill.
To turn a product idea into a design doc, you need to clarify demand reality, current workarounds, the most urgent user, and a narrow wedge. This structured brainstorming approach produces a high-signal document instead of code-first guessing.
Startup idea validation requires asking forcing questions about demand, status quo, desperate user specificity, wedge, surprise, and future-fit. These questions sharpen your venture direction and expose weaknesses before you commit resources.
Yes, YC office hours style brainstorming adapts to side projects, hackathons, and open source work. It shifts focus to builder delight, target audience, fastest shareable path, differentiation, and 10x additions to make your next direction concrete.
Validating demand for a startup strategy involves identifying the current workaround users rely on and testing desperate specificity. This diagnostic process ensures you are targeting an urgent problem before proceeding to implementation.
Finding the narrowest wedge for product design requires iterating through forcing questions about user discovery and the most urgent user. This method narrows your focus to a specific entry point that guarantees immediate traction.
No, this design doc process outputs only a structured document capturing decisions and sharpened direction, not code. It uses a fixed multi-phase prompting workflow with iterative questions to finalize your product strategy.
chenluhanConverts raw product input into a structured brief with defined components.
figmaTranslate Figma designs into UI code using design tokens and existing components.
ajsai47Validate product ideas with structured YC-style office hours diagnostics.
raphaelVRAGenerate structured product strategy documents using RICE, MoSCoW, Kano, OKR, or Positioning frameworks.
