Generate YC-style design docs with decision logs and next steps.
npx skills add https://github.com/VertaKhan/cs_gstack --skill office-hours-vertakhan
Please help me install this Agent Skill. Skill: office-hours Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/office-hours Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill office-hours-vertakhan
## What problem does it solve? YC Office Hours helps teams generate concrete, production-ready design docs from brainstorming prompts. It codifies a structured process to capture ideas, align stakeholders, and produce actionable plans without code.
## Core Features & Use Cases
### Quick Start Ask to brainstorm a product idea and generate a YC-style design doc.
High-intent search queries and answers about installing and using this skill.
To turn a vague product idea into a structured design doc, provide a clear brainstorming prompt and context on constraints. The process outputs a YC-style design doc outline, a decision log, and actionable next steps without requiring code.
To validate startup demand during early brainstorming, use a rapid ideation mode that transforms initial concepts into production-ready plans. This captures stakeholder alignment and produces structured validation plans for proposals.
Yes, you can use this for feature brainstorming on an existing product by applying builder mode. It facilitates design thinking to explore feasibility and outputs a structured plan and decision log for new features.
Before generating a YC-style design doc, you need a clear prompt outlining your product idea and specific context on project constraints. These inputs are required to produce accurate decision logs and plan outlines.
A decision log helps with product planning by codifying structured choices made during brainstorming. It captures stakeholder alignment and tracks feasibility validations, ensuring actionable plans remain transparent and exportable.
When generating design docs without writing code, the limitation is that outputs focus purely on structured planning and stakeholder alignment. You receive a plan outline and decision log rather than functional prototypes or technical implementation.
4tikhonovGuide exploratory conversations to capture goals, constraints, and success criteria.
dhruvbaldawaClarify ambiguous requirements through structured questioning and documentation.
fabioc-alohaPlan and manage projects with PMI/PMBOK and Agile templates.
royhenengelGenerate spec-driven implementation plans for software development tasks.
