gstack-openclaw-office-hours

Guides structured product discovery sessions that produce design documents before any code is written.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill gstack-openclaw-office-hours-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-office-hours
Source: https://github.com/raghavbadhwar/rstack/tree/main/openclaw/skills/gstack-openclaw-office-hours
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill gstack-openclaw-office-hours-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and founders often jump straight into building before validating whether an idea is worth pursuing, leading to wasted effort on products nobody needs. This Skill enforces a structured discovery process that diagnoses demand, challenges premises, and produces a design document instead of code. ## Core Features & Use Cases - Dual-mode diagnostic: Runs a rigorous Startup mode with six forcing questions about demand evidence, status quo, and target users, or a collaborative Builder mode for hackathons, learning, and side projects. - Premise challenge and alternatives: Forces explicit agreement on premises and generates 2-3 implementation approaches with effort, risk, and reuse analysis before recommending one. - Design doc output: Saves an approved design document to memory with problem statement, demand evidence, recommended approach, and one concrete next action. - Use Case: A founder says "I want to build an AI tool for developers." The Skill asks one question at a time, pushes past vague answers, challenges the premise, presents alternative approaches, and delivers a design doc with a concrete validation assignment. ## Quick Start Ask the agent to run office hours on your new product idea before writing any code.

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 startup idea before building it?

Run an office hours session that asks six forcing questions one at a time, covering demand evidence, current workarounds, target user specificity, narrowest paid wedge, observed user behavior, and future relevance. The session ends with a design doc and one concrete validation action.

How to brainstorm a product idea with an AI coding agent?

Invoke the office hours skill, which acts as a product-strategy partner and refuses to write code. It gathers context, asks about your goal, challenges premises, proposes 2-3 approaches with effort and risk estimates, and saves an approved design document.

Does this skill write code or scaffold projects?

No. The skill has a hard gate prohibiting any implementation, scaffolding, or code generation. Its only output is a design document saved to memory, plus a concrete real-world assignment for the user.

What is the difference between Startup mode and Builder mode?

Startup mode applies to founders and intrapreneurs and uses direct, evidence-demanding diagnostic questions about demand and users. Builder mode applies to hackathons, learning, and side projects, using generative questions focused on delight and fast paths to something shareable.

When should I not use an office hours discovery session?

Skip it when you already have a fully validated plan and need implementation, since the skill never writes code. Even with a formed plan it still runs premise challenge and alternatives generation, which adds little value for purely mechanical tasks.