office-hours

Name: office-hours
Availability: InStock
Author: antriksh-29

Draft structured design documents for startup ideas during office hours.

Updated Mar 24, 2026

Search Tags:#design-docs #design-brainstorming #phase-driven #office-hours #startup-design #build-plans

Ready to run

npx skills add https://github.com/antriksh-29/reddit-automation --skill office-hours-antriksh-29

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/antriksh-29/reddit-automation/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/antriksh-29/reddit-automation --skill office-hours-antriksh-29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YC founders and teams often need clear, shareable design documents to align on problems, approaches, and next steps without writing production code. This skill acts as a dedicated partner in drafting structured design docs during office hours sessions.

Core Features & Use Cases

Collaborative design documentation: translate a problem space into a formal design doc with sections for problem framing, approach, risks, and success criteria.
Phase-driven guidance: follows a structured questioning flow to surface demands, constraints, and decision milestones, ending with a concrete plan.
Readiness for review: outputs a polished artifact that can be shared with mentors, sponsors, or teammates for feedback and alignment.

Quick Start

Describe your startup idea and I will draft a YC-quality design doc outlining the problem, approach, and next steps.

Frequently Asked Questions about office-hours

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

FAQPage Schema

How do I draft a YC startup design doc without writing production code?▼

Draft a YC startup design doc by describing your idea during a structured office hours session. The skill translates your problem space into a formal document with problem framing, approach, risks, and success criteria.

What is the best way to structure design brainstorming for a startup idea?▼

Structure design brainstorming for a startup idea using phase-driven prompts. This enforces a questioning flow to surface demands, constraints, and decision milestones, ending with a concrete build plan.

Can I use this to generate build plans ready for mentor or teammate review?▼

Yes, you can generate build plans ready for mentor or teammate review. The output is a polished artifact outlining problem framing, scope, risks, and proposed steps to align stakeholders without production code.

How do you write a design document that includes problem framing and scope?▼

Write a design document including problem framing and scope through collaborative brainstorming. The skill applies phase-based prompts to explore the idea, define decision criteria, and output a complete, shareable design doc.

Does this approach work for aligning teams on next steps during office hours?▼

Yes, this approach works for aligning teams on next steps during office hours. It acts as a dedicated partner to co-create YC design docs, enforcing structured exploration to produce concrete build steps for team alignment.

When do I need a phase-driven design doc instead of immediately coding?▼

You need a phase-driven design doc instead of immediately coding when your team requires clear, shareable documentation to align on problems, approaches, and next steps before committing to production development.