office-hours

Name: office-hours
Availability: InStock
Author: jukqaz

Prompt for concrete constraints before executing fuzzy requests in Claude Code workflows.

Updated Aug 23, 2026

Search Tags:#workflow #clarification #scope #claude-code #ai-planning #prompt-guardrail

Ready to run

npx skills add https://github.com/jukqaz/stack-pilot --skill office-hours-jukqaz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/jukqaz/stack-pilot/tree/main/addons/stackpilot-dev-kit/claude/skills/office-hours
Command: npx skills add https://github.com/jukqaz/stack-pilot --skill office-hours-jukqaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid scope creep by prompting for constraints before executing fuzzy user requests.

Core Features & Use Cases

Guides the user to define the scope, boundaries, and next action lane (plan, execute, investigate, review, or verify) before proceeding.
Loads the OFFICE_HOURS.md reference for deeper guidance and enforces non-intrusive clarifications to keep interactions safe and predictable.

Quick Start

Ask clarifying questions to establish scope before taking any action.

Frequently Asked Questions about office-hours

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

FAQPage Schema

How do I clarify scope and prevent scope creep in Claude Code workflows?▼

To clarify scope and prevent scope creep in Claude Code workflows, use a prompt guardrail that asks for concrete constraints before execution. This ensures boundaries are defined before any action starts.

What is the best way to handle fuzzy user requests before AI planning?▼

The best way to handle fuzzy user requests before AI planning is to prompt for specific constraints and guide the request into an actionable lane like plan, execute, investigate, review, or verify.

Does Claude Code support enforcing non-intrusive clarifications for safe execution?▼

Yes, Claude Code supports enforcing non-intrusive clarifications for safe execution by disabling direct model invocation and loading a reference file to guide predictable interactions.

How do I route a vague development task to the correct action lane?▼

To route a vague development task to the correct action lane, prompt the user to define boundaries first, then guide the workflow into one of five lanes: plan, execute, investigate, review, or verify.

When should I not use a scope clarification prompt in my AI workflow?▼

You should not use a scope clarification prompt when your request already has strictly defined constraints, as the prompt guardrail is designed specifically to resolve ambiguity in fuzzy requests before execution.