gstack-openclaw-office-hours

Clarify product ideas and design directions before implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you pressure-test a product idea, clarify the real problem, and choose a direction before any implementation starts. It is designed to stop vague brainstorming from turning into premature code.

Core Features & Use Cases

  • Context gathering and diagnosis: Reviews the current situation, checks recent project context, and identifies the most relevant area to change.
  • Product challenge mode: Pushes founders and internal teams to define demand, status quo, target user, wedge, observation, and future-fit with concrete evidence.
  • Builder mode collaboration: Helps hobbyists, learners, and hackathon teams turn an idea into the coolest practical version and a clear plan for what to build next.
  • Design-doc output: Produces a structured design document with premises, alternatives, recommendations, open questions, and next steps instead of implementation work.

Quick Start

Tell this Skill your product idea or design direction and ask it to run an office-hours diagnostic and draft a design document.

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 my product idea before writing any code?

To validate a product idea before coding, you can run an office-hours diagnostic that pressure-tests your premise and outputs a structured design document with recommendations and next steps.

What is the best way to turn raw startup ideas into a design doc?

Turning raw startup ideas into a design doc involves a phased questioning process that challenges your demand, target user, and wedge, resulting in a structured document with premises, alternatives, and open questions instead of code.

Can I use founder coaching tools for hackathon brainstorming?

Yes, you can use this founder coaching approach for hackathon brainstorming. It features a builder mode that helps hackathon teams turn an idea into the coolest practical version and a clear plan for what to build next.

How do I challenge the premise of a product strategy?

To challenge a product strategy premise, apply a product challenge mode that pushes you to define demand, status quo, target user, wedge, and future-fit using concrete evidence before implementation begins.

Does idea validation work for internal intrapreneurship projects?

Yes, idea validation works for intrapreneurship projects. The diagnostic reviews the current situation, checks recent project context, and identifies the most relevant area to change before any implementation starts.

What should a product design document include for feature planning?

A product design document for feature planning should include premises, alternatives, recommendations, open questions, and next steps, generated through contextual review and premise challenge rather than immediate implementation.