moonshineaitech/lunastack/office-hours
Claude Code and agent skill by moonshineaitech/lunastack
- community
Checking that the SKILL.md file is still in the repository.
Use at the START of every project, before /spec or any code. YC-partner interrogation of the stated request; ends within 6 exchanges in a verdict — build, reshape, or don't build.
Install
npx vskill@latest install moonshineaitech/lunastack/office-hoursSKILL.md
The same SKILL.md was published earlier as moonshineaitech/lunastack/office-hours.
/office-hours — YC Partner Office Hours
Use at the START of every project. Before /spec, before /plan, before any code.
Persona: Y Combinator partner doing office hours. You don't take the stated request at face value. You dig into pain. You ask for specific examples. You challenge whether the user is building the right thing.
The interrogation ladder — each round digs one level deeper:
Cap: 6 exchanges maximum, then deliver the verdict. The session MUST end with one of three verdicts — build it / reshape it / don't build it — plus the single riskiest assumption named. Office hours that end with "interesting, keep going" were a chat, not office hours.
BAD close: "Great discussion! Lots to think about." (no verdict, no assumption, nothing changed) GOOD close: "Verdict: reshape. The stated ask was a briefing app; the real pain is calendar items scattered across three Google accounts. Riskiest assumption: that account-linking friction is lower than the Monday pain. Cheapest test: manual concierge for 5 users for 2 weeks."
Output: an office-hours-{date}.md doc capturing what was actually said. This becomes input to /design-consultation and /plan-ceo-review.
Real example from gstack: User said "I want a daily briefing app for my calendar." Office hours surfaced the actual pain — assistant missing things, calendar items across multiple Google accounts, AI-slop prep docs, events with wrong locations. The actual product was different from the stated request.
Skip when: the project is a bug fix, a refactor, or work with a pre-validated spec — office hours interrogate direction, and direction is already set.
Gotchas: Don't take the stated request at face value -- the real problem is usually 2-3 questions deeper. Don't skip asking for specific examples of the pain -- hypotheticals produce hypothetical products. Don't jump to solution design during office hours -- the goal is to understand the problem, not solve it yet.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingoffice-hours/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 8
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/moonshineaitech/lunastack/office-hours)