gstack-openclaw-office-hours

Run a structured office-hours session that asks six forcing questions about demand evidence, current workarounds, target users, and the narrowest paid wedge. The session produces a design document with premises, alternatives, and one concrete next action.

Ask what evidence proves someone wants it, what users do today to solve the problem, who the specific user is, and what the smallest payable version is. These questions expose weak demand before engineering effort is spent.

No. The skill has a hard gate prohibiting any implementation, scaffolding, or code generation. Its only output is a design document containing the problem statement, demand evidence, approaches considered, and next steps.

Yes. Builder mode handles hackathons, open source, learning, and fun projects with generative questions about the coolest version and fastest path to something shareable, ending in concrete build steps rather than business validation.

The diagnostic questioning phase is skipped, but the premise challenge and alternatives generation phases still run. You must confirm premises and choose between at least two implementation approaches before the design doc is written.