gstack-openclaw-office-hours

Generate formal design documents from structured product interrogation sessions.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill gstack-openclaw-office-hours-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-office-hours
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-office-hours
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill gstack-openclaw-office-hours-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founders and builders frequently waste time and resources building products no one wants because they skip structured idea validation before writing any code. This skill enforces disciplined product interrogation to de-risk concepts and align on real user demand before implementation begins.

Core Features & Use Cases

  • Dual operating modes: Startup diagnostic mode for founders and intrapreneurs, using six forcing questions to test demand, status quo, and market wedge; builder mode for hackathon participants, side project creators, and learners, acting as an enthusiastic design partner for brainstorming.
  • Structured output: Generates formal design documents with problem statements, evidence synthesis, alternative approaches, and concrete next steps, with no code or implementation artifacts produced.
  • Use cases: Run when asked to brainstorm a new product idea, validate if an idea is worth building, conduct "office hours" style product thinking sessions, or work through design decisions before starting development.

Quick Start

Use the gstack-openclaw-office-hours skill to run a structured product diagnostic for your new SaaS idea for freelance graphic designers to validate demand and identify your narrowest market wedge before building anything.

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 building anything?

Product idea validation is a structured diagnostic process that uses forcing questions to test demand, status quo, and market wedge before implementation begins. It de-risks concepts by challenging premises and analyzing alternative approaches to ensure real user demand exists.

What is YC-style office hours for product thinking?

YC-style office hours for product thinking is an interrogation framework that enforces disciplined product validation through premise challenges and demand testing. It delivers formal design documents with problem statements, evidence synthesis, and concrete next steps without generating any code.

Can I use this for hackathon brainstorming and side project ideas?

Hackathon brainstorming and side project ideas fit the builder mode, which acts as an enthusiastic design partner for idea generation. Startup founders and intrapreneurs use the separate diagnostic mode to run six forcing questions testing demand and identifying market wedge.

What's the best way to run pre-build planning for a new SaaS idea?

Pre-build planning for a new SaaS idea is best executed by running structured product interrogations that force questions about user demand and the narrowest market wedge. This process yields formal design documents with alternative approaches and concrete next steps instead of code artifacts.

Does product validation generate any code or implementation artifacts?

Product validation through this skill does not generate any code or implementation artifacts. It strictly produces formal design documents containing problem statements, evidence synthesis, alternative approaches, and concrete next steps to align on real user demand before development starts.

When should I not use structured product interrogation for idea validation?

Structured product interrogation should not be used when you are ready to write code and need implementation artifacts rather than design documents. It is designed exclusively for pre-build planning, idea brainstorming, and demand testing phases before any development begins.