How do I install the Office Hours skill?

Run npx skillmds@latest add itechdev-mx/office-hours in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Office Hours safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Office Hours?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Office Hours free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Office Hours?

ITECHDEV-MX (@itechdev-mx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Office Hours by itechdev-mx — Agent Skill

Name: Office Hours
Author: ITECHDEV-MX

Office Hours

Reframe a client request before any planning happens. Asks the user forcing questions, identifies the real product hiding inside the ask, and outputs a structured rewrite that the rest of the chain consumes. First step in story-creation pipelines.

ITECHDEV-MX 99a57c3 2.1 KB Updated Sep 17, 2026

File contents

When to Use

Use this skill as the first step of any story-creation chain under /Historias/. Trigger conditions:

The user asked to "redactar una historia" / "draft a story" / "feature spec" without first stating WHO/WHY/WHAT explicitly.
An RFP / client brief landed and we are about to price it.
Internal "we should do X" requests that haven't been validated.

Skip this skill only if the input already arrives in Connextra+Gherkin form — that's the contract for story-writer.

Rules

Iron Law: no fixes without investigation. Before reframing, restate the original request verbatim at the top of the artifact (under heading ## Original request) so the chain has the audit trail.
Identify the real product hiding inside the request. The user often asks for solution X but wants outcome Y. Name Y explicitly.
Ask at least three forcing questions about Who / Why / What success looks like. Do not assume answers. If the user is not present, list questions as ## Forcing questions (unanswered).
Output is structured Markdown with these sections in order: ## Original request, ## Reframed objective, ## Stakeholders, ## Forcing questions, ## What success looks like, ## Constraints we already know.
Word count target: 300–800. Below is too thin; above is leaking into the next agent's job.
Hand off to plan-ceo-review (position 1) by writing the artifact to /Historias/<slug>/0-office-hours.md and calling aria_artifact_save.

Verification

Artifact saved at /Historias/<slug>/0-office-hours.md
Sections in canonical order
Word count in [300, 800]
At least 3 forcing questions present (answered or not)
Original request quoted verbatim
No solutions proposed (that's autoplan's job)

---name: office-hoursdescription: Reframe a client request before any planning happens. Asks the user forcing questions, identifies the real product hiding inside the ask, and outputs a structured rewrite that the rest of the chain consumes. First step in story-creation pipelines.license: Apache-2.0---## When to UseUse this skill as the **first** step of any story-creation chainunder `/Historias/`. Trigger conditions:- The user asked to "redactar una historia" / "draft a story" / "feature spec" without first stating WHO/WHY/WHAT explicitly.- An RFP / client brief landed and we are about to price it.- Internal "we should do X" requests that haven't been validated.Skip this skill only if the input already arrives in**Connextra+Gherkin** form — that's the contract for `story-writer`.## Rules1. **Iron Law: no fixes without investigation.** Before reframing, restate the original request verbatim at the top of the artifact (under heading `## Original request`) so the chain has the audit trail.2. Identify the **real product hiding inside the request**. The user often asks for solution X but wants outcome Y. Name Y explicitly.3. Ask **at least three forcing questions** about Who / Why / What success looks like. Do not assume answers. If the user is not present, list questions as `## Forcing questions (unanswered)`.4. Output is structured Markdown with these sections in order: `## Original request`, `## Reframed objective`, `## Stakeholders`, `## Forcing questions`, `## What success looks like`, `## Constraints we already know`.5. Word count target: 300–800. Below is too thin; above is leaking into the next agent's job.6. Hand off to `plan-ceo-review` (position 1) by writing the artifact to `/Historias/<slug>/0-office-hours.md` and calling `aria_artifact_save`.## Verification- [ ] Artifact saved at `/Historias/<slug>/0-office-hours.md`- [ ] Sections in canonical order- [ ] Word count in [300, 800]- [ ] At least 3 forcing questions present (answered or not)- [ ] Original request quoted verbatim- [ ] No solutions proposed (that's `autoplan`'s job)

Frequently asked questions