office-hours

Transform vague startup ideas into structured design docs by extracting context, organizing problem statements, constraints, milestones, risks, and next steps into a decision-ready plan artifact. This approach grounds your design thinking and ensures your office hours session focuses on actionable planning rather than code implementation.

Design-focused planning for hackathon demos requires gathering context from repository notes and recent commits, then drafting a structured plan outlining goals and risks. This produces concrete, decision-ready documentation with clear milestones and owners, allowing you to quickly validate demo concepts and move forward.

Yes, you can generate an actionable plan from repository notes, CLAUDE.md, and TODOS for internal projects. The process collects project context to ground design decisions, then drafts a structured design doc that produces concrete tasks and assigns owners to move the idea forward after the session.

This design doc approach is specifically built for YC office hours partner sessions to help teams translate vague startup concepts into focused, action-ready documentation. It enforces frontmatter metadata and a clear delivery format, ensuring your project context is organized for quick, decision-ready validation.

Organize startup milestones and risks into a decision-ready format by extracting project context and structuring it into dedicated sections for problems, constraints, and next steps. This generates a concrete plan artifact with frontmatter metadata that enforces a clear delivery format for rapid decision-making.

You need a structured design doc instead of writing code when you have a startup concept, hackathon demo, or internal project that requires quick, decision-ready documentation. This approach enforces design thinking and context gathering to validate milestones and risks before committing to implementation.