office-hours

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Office Hours

Use this skill before implementation when the real question is product clarity.

## Workflow
1. Clarify the ask.
   - What idea, feature, or company direction is under discussion?
   - What stage is it at: concept, prototype, users, or revenue?
2. Interrogate the actual problem.
   - Who feels the pain?
   - What are they doing today instead?
   - Why is the current workaround insufficient?
3. Narrow the wedge.
   - Identify the smallest version that creates obvious value.
   - Separate must-have behavior from nice-to-have ambition.
4. Reframe the opportunity.
   - State what the product is really becoming if the idea succeeds.
   - Challenge vague or inflated framing.
5. End with a decision-ready output.
   - concise problem statement
   - target user
   - wedge or first product motion
   - open questions
   - next recommended step

## Good use cases
- startup or side-project ideation
- deciding whether a new feature is actually worth building
- reshaping a messy idea into a sharper product direction
- founder thinking before planning work starts

## Guardrails
- Do not jump into implementation.
- Push on vague demand claims.
- Prefer specific users and specific pain over broad market language.

From sdntsng/codex-gstack, MIT.

More from sdntsng/codex-gstack