gstack-deepseek-office-hours

Run DeepSeek API product critiques and save design notes locally.

Updated Apr 3, 2026

Search Tags:#deepseek #ai-assistant #product-management #design-note #office-hours #product-critique

Ready to run

npx skills add https://github.com/lyh2/gstack-deepseek --skill gstack-deepseek-office-hours

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-deepseek-office-hours
Source: https://github.com/lyh2/gstack-deepseek/tree/main/gstack-deepseek-office-hours
Command: npx skills add https://github.com/lyh2/gstack-deepseek --skill gstack-deepseek-office-hours

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DeepSeek-first product brainstorming for token-heavy projects. This skill runs a YC-style product critique through the DeepSeek API and writes a design note, avoiding heavy ideation on the host model.

Core Features & Use Cases

Structured critique workflow: Leverages the DeepSeek API to identify core user problems, challenge assumptions, and outline a wedge approach.
Design-note generation: Produces a shareable design note that documents insights, decisions, and recommended next steps.
Local project traceability: Saves outputs locally (e.g., in ~/.gstack/projects) for audit and reuse.

Quick Start

Initiate the DeepSeek office-hours workflow on your project to generate a critique and save a design note locally.

Frequently Asked Questions about gstack-deepseek-office-hours

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

FAQPage Schema

How do I run a YC-style product critique on my project idea?▼

Product critique through DeepSeek involves identifying core user problems, challenging assumptions, and outlining a wedge approach. It leverages the DeepSeek API to process your project context and generate actionable insights for product management.

Can I generate a design note for CEO and engineering reviews using AI?▼

Generating a design note for CEO and engineering reviews is supported by producing a shareable document that records insights, decisions, and recommended next steps. This note is saved locally for audit and reuse.

How does the DeepSeek API handle missing API keys or ambiguous project context?▼

Handling missing API keys and ambiguous project context is managed gracefully by the workflow. If inputs are missing or unclear, the skill processes the critique without failing, ensuring stable execution and saving outputs locally.

Where are DeepSeek product critique outputs saved locally?▼

Critique outputs are saved locally in the ~/.gstack/projects directory with a timestamp. This ensures local project traceability for future audit and reuse.

Do I need a DeepSeek API key to perform a wedge analysis on my project?▼

A DeepSeek API key is needed to perform a wedge analysis because the skill processes the critique through the DeepSeek API. However, the workflow gracefully handles missing keys to avoid blocking your process.

What is the best way to brainstorm token-heavy product ideas without overloading the host model?▼

Using a DeepSeek-first product brainstorming approach is the best way to handle token-heavy projects. This skill executes the critique through the DeepSeek API and writes a design note, avoiding heavy ideation on the host model.