Ucts Office Hours

Product strategy session with 6 forcing questions. Reframes the problem, challenges premises, generates implementation approaches. Works directly in OpenClaw...

Security Scan

An instruction-only conversational skill whose requested capabilities and instructions align with its stated purpose and do not ask for extra credentials or installs.

Purpose & Capability

The name and description (product strategy office hours) match the SKILL.md instructions. No binaries, env vars, or config paths are required — nothing extraneous is requested for an interactive planning session.

Instruction Scope

The instructions are narrowly scoped to running a guided conversation (six questions, pushback, generate approaches, recommend one). They do include a single cross-skill dispatch suggestion (`Load UCTS. Run /ucts guide <refined description>`). Verify what the referenced UCTS/Claude Code session does before allowing dispatch, since that could invoke other behavior or handle data differently.

Install Mechanism

No install spec or code files — instruction-only skills have minimal on-disk footprint and low installation risk.

Credentials

The skill declares no environment variables, credentials, or config paths. There is no disproportionate credential or system access requested.

Persistence & Privilege

always:false (default) and no special privileges requested. The skill can be invoked autonomously per platform defaults, which is expected for conversational skills; this is not combined with any broad credential access.

Assessment

This skill is a low-risk, instruction-only conversational helper and appears coherent with its stated purpose. Before installing, confirm whether you have or trust the referenced 'UCTS'/Claude Code capability — the SKILL.md suggests dispatching to it, and you should verify what that other skill does and how it handles data. As with any planning skill, avoid entering sensitive credentials or private PII into the conversation. If you want stricter control, keep autonomous invocation disabled at the platform level or vet the UCTS target it may call.

Run a structured product strategy session. This is a conversational skill — talk directly with the user.

The 6 Forcing Questions

Ask each question. Push back on vague answers. Demand specifics.

1. What's the specific pain?

Not hypothetical. Real examples. Who screamed? What broke? When did it last happen? If the user says "it would be nice to have X" — push: "What happens TODAY without X?"

2. Who experiences this most acutely?

Which user persona? How often? What's the cost of the status quo (in time, money, frustration)? "Everyone" is not an answer. Find the single person who suffers most.

3. What's the current workaround?

If there is one, it tells you the actual need. If there isn't, why not? Workarounds reveal the minimum viable solution.

4. What does the 10-star experience look like?

Dream big. If this worked perfectly — magic wand — what would it do? Then cut: what's the 7-star version? The 5-star? The 3-star MVP?

5. What's the narrowest wedge?

The smallest possible thing that proves the concept works. Not the full vision — the first proof. It should be buildable in one session. If it takes a week, it's too big.

6. What's the one metric?

Single number that tells you it's working. Not three metrics. One. "Users" is not a metric. "Daily active users who complete the core flow" is.

After the Questions

1. Challenge the framing. Push back on what the user SAID they want vs what they ACTUALLY described needing.
2. Generate 3 approaches with effort estimates:
   • Quick & dirty (hours)
   • Solid MVP (days)
   • Production-grade (weeks)
3. Recommend one. Be opinionated. "Start with approach 1, validate with the metric, then upgrade to approach 2."
4. If a Claude Code session is needed, generate the dispatch: Load UCTS. Run /ucts guide <refined description>