gstack-openclaw-office-hours

Run an office-hours session that asks six forcing questions about demand evidence, current workarounds, target users, and the narrowest paid wedge. The session ends with a design document and one concrete real-world assignment.

Ask what evidence proves someone wants it, what users do today to solve the problem, who the specific user is, and what the smallest paid version looks like. This Skill walks through each question one at a time.

No. It has a hard gate against implementation and only produces design documents. Its output is a structured design doc with premises, alternative approaches, and a recommended direction.

Yes. Builder mode handles hackathons, learning projects, open source, and fun builds with generative questions about delight and the fastest path to something shareable, instead of the startup diagnostic.

The session produces a design document, not market data or working software. It depends on the honesty and specificity of your answers, and validation still requires real-world action like talking to users or collecting payments.