skills.rest
andrew-t-james
andrew-t-jamesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

office-hours

Compile project goals, constraints, and decisions into a structured design document.

Updated Jul 3, 2025
Search Tags:#design#planning#architecture#requirements#stakeholders#design-doc#office-hours
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill office-hours-andrew-t-james
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/office-hours
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill office-hours-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Office hours sessions often produce vague notes and scattered artifacts. This Skill compiles the discussion into a cohesive design document that clarifies goals, constraints and chosen approaches.

Core Features & Use Cases

  • Drafts a complete design doc from live discussions, gate reviews, and stakeholder input.
  • Bridges context gaps by extracting goals, constraints, risks, and decisions.
  • Use Case: during a project kickoff, run this skill to generate a design doc that your team can review in a single meeting.

Quick Start

Provide the project goal, existing artifacts, and constraints to generate a complete design doc ready for review.

Frequently Asked Questions about office-hours

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn stakeholder meeting notes into a structured design doc?▼

You can compile stakeholder meeting notes into a structured design doc by providing project goals, existing artifacts, and constraints to generate a document with context, requirements, decisions, risks, and next steps.

What is the best way to document architecture discussions from cross-functional teams?▼

Documenting architecture discussions is best handled by translating project context and stakeholder inputs into a ready-to-review design document that bridges context gaps and clarifies chosen approaches.

How do I create a design document for early-stage product planning?▼

To create a design document for early-stage product planning, supply the project goal and known constraints to draft a complete design doc ready for team review during a project kickoff.

What do I need to generate a design doc from office hours sessions?▼

To generate a design doc from office hours, you need to provide user-provided goals, existing artifacts, constraints, and decisions as inputs for the skill to process.

Can I use this to prepare for a project kickoff design review?▼

Yes, you can use this for a project kickoff design review by running it beforehand to generate a complete design doc that your cross-functional team can review in a single meeting.

What sections are included in a generated design document?▼

A generated design document includes structured sections for context, requirements, decisions, risks, and next steps extracted from your project goals and stakeholder inputs.

Related Skills

Explore More Design & Creative Skills→
soeiroosoeiroo

design-brief

Create structured design briefs with problem statements, audience, constraints, and success criteria.

Community
Intermediate
vnmoorthyvnmoorthy
2

plan-eng-review

Review engineering plans for architecture, data flow, edge cases, tests, and performance.

Community
Advanced
dogeareddogeared

office-hours

Convert startup goals and constraints into structured design docs for YC office hours.

Community
Advanced
hachejhachej
45

grill-with-docs

Interrogate domain models to identify gaps and generate ADRs and glossaries.

Community
Intermediate