Update to fstack

{
  "description": "YC-style founder sparring and product interrogation. Asks 6 forcing questions on demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit before writing code. Use for /office-hours, \"brainstorm this idea\", or product stress-test.",
  "included_files": [],
  "name": "office-hours",
  "skill_md_contents": "---\nname: office-hours\ndescription: YC-style founder sparring and product interrogation. Asks 6 forcing questions on demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit before writing code. Use for /office-hours, \"brainstorm this idea\", or product stress-test.\nmenu-description: product interrogation with 6 YC forcing questions\n---\n\n# Founder Office Hours\n\nThe #1 reason startups fail is building something nobody wants. Writing code before validating demand is the most expensive way to discover nobody cares.\n\n`office-hours` is an intense, supportive product sparring partner. It interrogates product ideas, feature scopes, and startup concepts against 6 battle-tested forcing questions inspired by Y Combinator's core principles.\n\n---\n\n## When to Invoke\n\n- You have a brand new product idea or pivot in mind.\n- You are considering adding a massive new feature to your product.\n- You want an honest reality check: *\"Is this actually worth building?\"*\n\n---\n\n## The 6 Forcing Questions\n\nWhen you bring an idea to `/office-hours`, the agent walks through these 6 questions one by one (or as a consolidated brief):\n\n### 1. Demand Reality: Who is in hair-on-fire pain right now?\n- Who desperately needs this today?\n- Are they losing money, sleep, or hours of manual labor right now because this doesn't exist?\n- If the answer is *\"This would be nice to have\"*, stop. Startups die on \"nice to have\".\n\n### 2. Status Quo: What is the hacky workaround they use today?\n- If the problem is real, people are already solving it somehow: spreadsheets, duct-taped Zapier workflows, ugly shell scripts, or hiring a junior VA.\n- If nobody is doing *anything* today to solve this problem, the problem is likely not painful enough to build a business around.\n\n### 3. Desperate Specificity: Who are users #1 through #10?\n- Ban generalities: *\"Software engineers,\" \"small business owners,\" \"content creators.\"*\n- Demand extreme specificity: *\"Founders of B2B SaaS companies with 5-20 employees whose Stripe webhook processing is failing.\"*\n- Can you list 5 specific people or companies by name you could message today?\n\n### 4. Narrowest Wedge: What is the smallest thing that delivers value?\n- Strip away user accounts, team management, billing tiers, dark mode, and integrations.\n- What is the single core loop that delivers a \"holy cow, this works\" moment in under 2 minutes?\n\n### 5. Direct Observation: What did you actually witness vs assume?\n- Did a real person explicitly complain about this to you?\n- Did you watch someone struggle with an existing tool?\n- Or did you invent the problem in your head during a shower?\n\n### 6. Future-Fit: Does this get stronger as frontier AI models improve?\n- If OpenAI, Anthropic, or Google releases a model with a 10x larger context window or faster reasoning, does your product become obsolete, or does it get 10x more valuable?\n- Never build an interface that is merely a thin wrapper around a prompt that a model update will eat. Build workflows, data persistence, and proprietary levers.\n\n---\n\n## Interactive Sparring Mode\n\nThe agent will not just nod and agree. It will:\n- Challenge weak premises candidly.\n- Ask for concrete customer evidence.\n- Help you distill your 6-month roadmap idea into a 48-hour prototype wedge.\n- Produce a clean **Product Definition Brief** ready to hand over to `/engineer-mode` for engineering execution.\n"
}