Guide teams through structured problem discovery and design-doc creation.
npx skills add https://github.com/ibalasite/gstack --skill office-hours-ibalasite
Please help me install this Agent Skill. Skill: office-hours Source: https://github.com/ibalasite/gstack/tree/main/office-hours Command: npx skills add https://github.com/ibalasite/gstack --skill office-hours-ibalasite
This skill provides a guided Office Hours-style session to rapidly align teams around a problem, surface explicit demand signals, and generate a formal design doc that documents decisions, constraints, and next steps.
Guide me through a YC Office Hours session and produce a completed design doc.
High-intent search queries and answers about installing and using this skill.
A YC office hours session structured for design docs uses forced-question flows to gather context, define the problem, and generate a written plan. It guides teams through phase-driven coaching to extract testable hypotheses and outputs a decision-ready document.
The best way to frame startup problems during rapid problem discovery is using structured, evidence-based questioning. This coaching approach extracts explicit demand signals and forces teams to define concrete, testable hypotheses before committing to a written plan.
Yes, this structured problem-solving flow is mode-agnostic and works for hackathons, open-source projects, and intrapreneurship. It adapts to any team needing rapid alignment, evidence-based problem framing, and a living design document for review.
Design docs help teams align by documenting decisions, constraints, and next steps gathered during problem discovery. They provide a living plan that captures testable hypotheses and explicit demand signals, ensuring everyone reviews the same evidence-based framework.
No, this office hours coaching flow requires no external frameworks or dependencies. It uses a predefined questioning flow and design-doc templates to guide context gathering, problem definition, and plan execution with user confirmation prompts.
You should avoid using a forced-question flow for design doc creation when your team already has a fully defined, testable hypothesis and a formalized plan. It is designed for rapid problem framing and alignment, not for documenting already finalized decisions.
Euraika-LabsGenerate a structured game concept document from an initial idea.
jlawsExecute written plans in task batches with review checkpoints and verification.
YaugourtConverts product ideas into YC-style design docs with structured decisions and tradeoffs.
slgoodrichValidate product problems and solutions with experiments and validation checklists.
