office-hours

Generate structured design docs for startup ideas before coding.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/bajajvinamr/little-wins --skill office-hours-bajajvinamr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/bajajvinamr/little-wins/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/bajajvinamr/little-wins --skill office-hours-bajajvinamr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founders often start with vague ideas and lack a structured plan to validate and ship. This skill generates clear, design-first documentation that communicates goals, constraints, risks, and proposed solutions before any code is written.

Core Features & Use Cases

  • Structured design documents that capture problem, opportunities, success metrics, constraints, and a plan.
  • Phase-driven brainstorming for prioritization, risk assessment, and decision criteria.
  • Use Case: a founder wants to scope a new feature and needs a plan that can be reviewed by teammates before prototyping.

Quick Start

Describe your startup idea and I will generate a structured design doc outlining goals, constraints, risks, and a plan.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I create structured design docs for startup ideas?

Structured design docs for startup ideas are generated by applying a consistent outline covering problem statements, proposed approaches, risks, milestones, and rationale to capture goals and constraints before coding.

What is the best way to validate a startup concept before writing code?

The best way to validate a startup concept before coding is generating a design-first document that captures problems, opportunities, success metrics, and constraints to produce a clear, reviewable plan for teammates.

How do I structure brainstorming for early-stage startup features?

You structure brainstorming for early-stage startup features by applying a phase-driven process for prioritization, risk assessment, and decision criteria to produce a reviewable plan before prototyping.

Does this approach capture risks and milestones for decision-making?

Yes, this approach captures risks and milestones for decision-making by enforcing a consistent design doc outline that includes proposed approaches, rationale, and success metrics for early-stage concepts.

Can I use this for scoping a new feature plan for teammates?

Yes, you can use this for scoping a new feature plan for teammates by generating a structured design document that outlines goals, constraints, and risks for review before prototyping begins.