A normalized ai-workflow adaptation of gstack's office-hours workflow. Use when a request starts as a vague idea and needs reframing into a concrete product direction, narrow wedge, and execution-ready design doc.
Use this skill before planning or implementation when the user has an idea, a rough feature, or an unclear product direction.
This is a normalized adaptation of garrytan/gstack's office-hours workflow.
It keeps the product-thinking structure, but removes gstack-specific telemetry, local state, and upgrade logic.
Turn a vague request into a design artifact that downstream planning and execution can use.
At the end, write a design note to:
.ai-workflow/artifacts/gstack/office-hours/<date>-<topic-slug>.md
The note should include:
Default placement: ThreadMessage.Metadata.
Do not default this skill to WorkItem execution.
Reuse these keys:
artifact_namespace = gstackartifact_type = design_docartifact_format = markdownartifact_relpath = .ai-workflow/artifacts/gstack/office-hours/<date>-<topic-slug>.mdartifact_title = a short human-readable titleproducer_skill = gstack-office-hoursproducer_kind = skillsummary = a 1 to 2 sentence design-note summaryIf the design note is complete, recommend the next appropriate step:
gstack-plan-ceo-review if scope and product direction need pressure-testing.gstack-plan-eng-review if the product direction is clear and implementation planning should start.Good output does not repeat the user's wording mechanically. Good output reframes the problem, sharpens the wedge, and leaves behind a reusable artifact.