skills.rest
0xUrsanomics
0xUrsanomicsCOMMUNITY
Explore all skills by this author →
GitHub

office-hours

Interrogate user requirements to identify hidden assumptions and validate project goals.

2|Updated Jul 22, 2026
Search Tags:#planning#scoping#requirements#validation#strategy#decision-making
One-click install
npx skills add https://github.com/0xUrsanomics/utopia-os --skill office-hours-0xursanomics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/0xUrsanomics/utopia-os/tree/main/skills/office-hours
Command: npx skills add https://github.com/0xUrsanomics/utopia-os --skill office-hours-0xursanomics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents the common failure of building from vague or poorly defined requirements by forcing the user to clarify assumptions and goals before any code is written.

Core Features & Use Cases

  • Goal-Type Mapping: Adjusts the rigor of questioning based on whether the project is Revenue, Infrastructure, Content, Personal, or a Side-quest.
  • Forcing-Question Framework: Uses a structured, six-question protocol to surface hidden assumptions, verify pain points, and define success metrics.
  • Use Case: Before starting a new feature, use this skill to gut-check if the request is based on real user pain or hypothetical assumptions, ensuring the agent builds the right solution.

Quick Start

Trigger the office hours skill to sharpen the requirements for the new project idea I am planning to build.

Frequently Asked Questions about office-hours

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate project requirements before starting development?▼

Validating project requirements involves a structured interrogation protocol that maps goals to categories like revenue or infrastructure, applying forcing questions to surface hidden assumptions and define success metrics.

What is the best way to scope a new feature to prevent building the wrong solution?▼

Scoping a new feature effectively requires clarifying assumptions and goals before any code is written, using a six-question forcing framework to verify if the request is based on real user pain or hypothetical assumptions.

How does requirement validation work for different types of project categories?▼

Requirement validation adjusts questioning rigor dynamically based on the project category, ensuring appropriate feedback whether the project is an infrastructure build, a revenue-generating task, or an exploratory side-quest.

Do I need project context and memory systems to use structured requirement interrogation?▼

Yes, structured requirement interrogation requires integration with memory systems and project context to provide tailored, high-rigor feedback on project framing and accurately identify hidden assumptions.

What forcing questions should I ask to surface hidden assumptions in project planning?▼

To surface hidden assumptions in project planning, ask a structured set of six forcing questions designed to verify pain points, define success metrics, and clarify goals before implementation begins.

Related Skills

Explore More Product & Management Skills→
artsmcartsmc
3

memorybank-initialize

Create six core Memory Bank documentation files with starter templates.

Community
Intermediate
gkganesh12gkganesh12
1

gk-brainstorm

Transforms project concepts into validated, buildable BRIEF.md specifications via structured discovery workflows.

Community
Advanced
zzafergokzzafergok
1

product-strategy-lead

Align product strategy with business goals through OKR cascading and financial modeling.

Community
Advanced
vndeevndee
3

interactive-clarify

Enforce interactive AskUserQuestion rounds with 1-4 questions and 2-4 options.

Community
Advanced