Structure planning conversations and generate a design doc from forcing questions.
npx skills add https://github.com/cropsgg/skills --skill office-hours-cropsgg
Please help me install this Agent Skill. Skill: office-hours Source: https://github.com/cropsgg/skills/tree/main/skills/planning/office-hours Command: npx skills add https://github.com/cropsgg/skills --skill office-hours-cropsgg
The Skill helps teams avoid scope creep by forcing structured problem framing before any code is written.
Answer the six forcing questions and generate a written design doc ready for review.
High-intent search queries and answers about installing and using this skill.
To structure product planning conversations before coding, use enforced forcing questions to elicit user needs and constraints, then auto-generate a design doc capturing the problem, wedge, scope, and non-goals for stakeholder alignment.
Preventing scope creep during early-stage ideation requires structured problem framing via a forcing questions workflow, ensuring precise user needs are documented in a design doc before development begins.
Generate a design doc for greenfield initiatives by answering six forcing questions, which automatically produces a written output detailing the problem, wedge, scope v1, non-goals, and open questions ready for review.
Yes, you can use forcing questions to align stakeholders during product kickoff sessions, as the workflow surfaces decision criteria and generates an explicit design doc path for review.
Process documentation for early-stage product management should include the problem statement, wedge, scope v1, non-goals, and open questions, all captured within an auto-generated design doc.
You need a design doc instead of starting development when working on greenfield initiatives or early-stage features where a structured documentation flow is not yet established, ensuring scope is defined.
misty-stepGuide raw ideas through six forcing questions to produce sharpened problem statements.
wsxwj123Organize early-stage ideas into a structured design plan.
FrantssCoordinate multi-session project execution through a shared issue-tracker ticket map.
arbisoftValidate feature rationale with diagnostic questions and evaluation modes.
