skills.rest
pistosmin
pistosminCOMMUNITY
Explore all skills by this author →
GitHub

office-hours

Guide founders through structured questions to generate design docs with hypotheses, risks, and success criteria.

Updated Mar 24, 2026
Search Tags:#startup#design-doc#design-thinking#product-discovery#ask-user-question#office-hours
One-click install
npx skills add https://github.com/pistosmin/base-one --skill office-hours-pistosmin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/pistosmin/base-one/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/pistosmin/base-one --skill office-hours-pistosmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides founders to convert ideas into concrete design docs by leading them through structured, forcing questions and a documented plan.

Core Features & Use Cases

  • Phase-based discovery: context gathering (Phase 1) followed by startup-mode diagnostics (Phase 2) to surface constraints and next steps.
  • AskUserQuestion framework: one-question-at-a-time prompts that push for specificity and real-world evidence.
  • Design-doc generation: outputs a living design doc capturing hypotheses, risks, success criteria, and actionable next steps.
  • Collaboration-first workflow: suitable for founders, product managers, and teams seeking a documented blueprint before building.
  • Use cases include ideation, product strategy alignment, and internal project approvals.

Quick Start

Describe your idea and goals, and I will guide you through Phase 1 context gathering to generate a design doc.

Frequently Asked Questions about office-hours

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a startup idea into a structured design doc?▼

To turn a startup idea into a design doc, you engage in a guided, question-led session that gathers context and surfaces constraints, resulting in a formal document with clear hypotheses, risks, and success criteria.

What is the best way to document product discovery and design thinking for an early-stage project?▼

Product discovery for early-stage projects is best documented through a phased, AskUserQuestion-driven process that forces specificity, capturing real-world evidence and actionable next steps in a living design doc.

Can I use this guided design doc process for hackathon demos and internal project approvals?▼

Yes, this guided design doc process applies to hackathon demos, intrapreneurship projects, and internal project approvals, helping teams establish a documented blueprint and clarify design direction before building.

How does the AskUserQuestion framework work for creating startup design docs?▼

The AskUserQuestion framework works by presenting one-question-at-a-time prompts that push founders for specificity and real-world evidence during context gathering and startup-mode diagnostics.

Do I need any specific technical tools or dependencies to start generating a design doc?▼

No external technical tools or dependencies are required to start generating a design doc; you simply describe your idea and goals to begin the Phase 1 context gathering process.

Related Skills

Explore More Product & Management Skills→
WeZZardWeZZard
22

brainstorming

Clarify goals and generate initial design directions through collaborative brainstorming.

Community
Advanced
4tikhonov4tikhonov
3

intent-capture

Guide exploratory conversations to capture goals, constraints, and success criteria.

Community
Basic
asmartbearasmartbear
4

asb-interview-learning

Synthesize customer interview debriefs to update working hypotheses with evidence.

Community
Advanced
The13thNodeThe13thNode
3

problem-validation

Validate startup problem existence, pain level, and solvability during customer discovery interviews.

Community
Intermediate