gstack-openclaw-office-hours

Validate product ideas with six diagnostic questions and structured design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founders and builders frequently waste time building solutions for problems no one actually has, because they skip rigorous validation of demand and problem severity before writing code. This skill eliminates that risk by enforcing structured product interrogation and design planning before any implementation begins.

Core Features & Use Cases

  • Dual operating modes: Startup diagnostic mode for founders and intrapreneurs with six forcing questions to test demand, status quo, user specificity, narrowest wedge, user observation, and future product fit; builder mode for side projects, hackathons, and learning with enthusiastic brainstorming to refine ideas.
  • Structured design doc output: Produces a clear, actionable design document instead of code, so you have a validated plan to reference before building.
  • Use case: Use it when you have a new product idea and aren't sure if it's worth building, when preparing for a hackathon and need to narrow your scope fast, or when you want to think through design decisions before investing time in development.

Quick Start

Use the gstack-openclaw-office-hours skill to run a product diagnostic for my new tool that helps freelance designers track client revisions and feedback across multiple projects.

Frequently Asked Questions about gstack-openclaw-office-hours

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

FAQPage Schema
How do I validate a product idea before writing any code?

To validate a product idea before coding, you can use structured diagnostic questions that test demand, status quo, and user specificity. This approach enforces rigorous product-solution fit validation to eliminate wasted development effort on solutions no users want.

What is the best way to narrow feature scope for a hackathon project?

The best way to narrow feature scope for a hackathon project is to use a brainstorming mode that interrogates your idea. This helps builders quickly refine concepts, narrow the scope to the narrowest wedge, and produce a structured design document before development begins.

Can I use YC-style office hours to test demand for a side project?

Yes, you can use YC-style office hours to test demand for a side project. It offers a dual operating mode that provides enthusiastic brainstorming support specifically for side projects and learning use cases to help refine ideas without generating implementation code.

Does product validation generate a design document or implementation code?

Product validation generates a structured design document rather than implementation code. It produces a clear, actionable design plan covering user observation and future product fit, giving you a validated reference to consult before investing time in development.

What questions should I ask to test problem-solution fit for a startup?

To test problem-solution fit for a startup, you should ask six forcing diagnostic questions covering demand, status quo, user specificity, narrowest wedge, user observation, and future product fit. This structured interrogation ensures you avoid building unwanted solutions.