/office-hours | Sharpen the idea and product direction with YC-style questions | Problem definition · sorting the conversation |
/spec | Turn vague requirements into a detailed, actionable spec | Writing requirement and screen specs |
/plan-ceo-review | Review product value, scope and priority from a CEO view | Confirming MVP scope |
/plan-design-review | Review the UI/UX plan from a designer's view | Adding screen states · design concept |
/plan-eng-review | Review architecture, data flow, exceptions and test plan | Data/API contract · cross-audit |
/autoplan | Run CEO → design → engineering → DX review in one go | After you're used to the individual reviews |
/plan-devex-review | Review the developer-experience plan for APIs, CLIs, SDKs and docs | Check API docs (optional) |
/diagram | Turn descriptions into Mermaid, Excalidraw, SVG or PNG diagrams | Order flow · state transition diagram |
/make-pdf | Convert Markdown to PDF, HTML or DOCX | Spec package for submission |
/design-consultation | Propose a product design system and visual direction | Design concept (optional) |
/document-generate | Write missing docs using the Diataxis approach | Improve README · guides |
/review | Code review of the current branch or changes | Advanced: after building |
/investigate | Investigate the root cause of a bug, then fix it | Advanced: defect cause analysis |
/qa-only | Write only a QA report, without changes | Advanced: service verification table |
/qa | Test a web app and fix the bugs found | Advanced: fix after approval |
/careful · /freeze | Warn about risky commands · block edits outside the chosen folder | Protect code during planning |
/context-save · /context-restore | Save and restore work progress | When continuing the 2-day work |
/ship · /retro | Tests · review · create PR · write retro | Advanced: wrap-up |