Generate a design document and handoff plan from structured office-hours prompts.
npx skills add https://github.com/onlypfachi/chief --skill office-hours
Please help me install this Agent Skill. Skill: office-hours Source: https://github.com/onlypfachi/chief/tree/main/office-hours Command: npx skills add https://github.com/onlypfachi/chief --skill office-hours
This skill guides you through structured, phase-based office hours to produce design docs and a clear handoff plan for startups, builders, and learning projects.
Describe your project goal and current status to start a design-session flow.
High-intent search queries and answers about installing and using this skill.
A YC office hours design doc is created through a phase-driven session that prompts you for concrete user problems, demand signals, and constraints to produce a production-ready document for team handoff. You describe your project goal to initiate the structured flow.
A phase-driven design session is a structured questioning process that elicits target users and problem constraints to generate a draft design document ready for mentor review and handoff. It guides builders through sequential phases to clarify project scope.
Yes, this structured design doc flow supports startups, intrapreneurship, hackathons, and learning projects by synthesizing founder signals and generating YC-style persuasive closing notes for clear next steps. It requires your inputs on demand and constraints to function.
To start a design handoff flow, you provide prompts and inputs about your current project status, problem space, users, and constraints. The session then coordinates phase-based questions to elicit concrete details and produce a draft design document ready for approval.
Generating a production-ready office hours design doc requires inputs about your target users, demand signals, problem definition, and project constraints. These inputs fuel the phase-driven questions that ultimately synthesize founder signals into a structured handoff plan.
Automated design thinking docs require you to accurately articulate your problem and constraints upfront; without concrete inputs about demand and users, the generated design document may lack the depth needed for a successful team handoff. It produces a draft for review, not a final approved plan.
CapatainaGenerates a VISION.md fileCapturing project goals, scope, and design intent from guided team discussions.
xiduzoPlan holistic feature designs and write Design Handoff into the Feature issue.
hacketApply 10+ thinking frameworks to analyze articles and extract insights.
AkbarDevopFacilitate structured brainstorming and design thinking sessions for product development.
