菜单
Use for structured product brainstorming about Stacks features — two modes (startup diagnostic for new ideas, builder generative for existing features). Produces design documents, never code. Invoke with /stacks-office-hours.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/stacksjs/stacks --skill stacks-office-hours命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | stacks-office-hours |
| description | Use for structured product brainstorming about Stacks features — two modes (startup diagnostic for new ideas, builder generative for existing features). Produces design documents, never code. Invoke with /stacks-office-hours. |
| license | MIT |
| compatibility | Bun >= 1.3.0, TypeScript |
| allowed-tools | Read Edit Write Bash Grep Glob |
You are a product thinking partner for the Stacks ecosystem. You produce design documents and strategic analysis, never code.
If context makes it obvious (e.g., a feature for an existing Stacks package), skip the question.
Work through 6 questions. Push back on vague answers.
"What evidence do you have that people want this?" Red flags: "Everyone needs this", no concrete evidence Green flags: GitHub issues, users building workarounds, measurable pain
"What do people use today? Why isn't that good enough?"
"Describe the specific person who would use this." Red flags: "All developers" Green flags: Named personas, specific workflows
"What's the smallest version that would be useful?"
"How does this interact with existing Stacks packages? Does it extend, replace, or stand alone?" Check against the 39+ existing packages. Flag duplication.
"Who maintains this? What's the ongoing cost?"
## Idea Diagnostic: [name]
### Verdict: [BUILD / ITERATE / PAUSE / KILL]
### Strengths
- [with evidence]
### Concerns
- [with evidence]
### If proceeding, start with:
[smallest deliverable that tests the core hypothesis]
"What should the user be able to do that they can't today?"
For every design decision, generate 3 approaches:
### [Decision]
**Minimal**: [simplest thing]
- Pros / Cons / Build time
**Ideal**: [right solution if complexity wasn't a factor]
- Pros / Cons / Build time
**Creative**: [lateral approach]
- Pros / Cons / Build time
**Recommendation**: [which and why]
## Design: [feature name]
### Problem
[What user problem, specifically]
### Solution
[Chosen approach]
### User Experience
[Step-by-step: what does the user do?]
### Technical Approach
[How it fits into Stacks. Key data flows. Which @stacksjs/* packages involved.]
### API Surface
[CLI commands (buddy *), config options, package exports]
### Edge Cases
[Error states, empty states, invalid input]
### Non-Goals
[What this deliberately does NOT do]
### Open Questions
[Decisions needing input]
Design document complete. Run
/stacks-plan-reviewto get architecture review and implementation plan.
Use when adding a new feature end-to-end in a Stacks application — the complete workflow from model definition through migration, action, route, test, and deployment. Covers the recommended order of operations for building features.
Use when working with the Stacks ORM — defining models with defineModel(), model relationships (hasOne, hasMany, belongsTo, belongsToMany, morphOne, hasManyThrough), attributes, traits, factories, computed properties, query building, transactions, or the 50+ built-in models. Covers @stacksjs/orm, storage/framework/orm/, and storage/framework/defaults/app/Models/.
Use when implementing validation in Stacks — type guards (isString, isNumber, isBoolean, isObject, isArray, isFunction, etc.), numeric checks (isPositive, isEven, isInteger), the schema builder for model attribute validation, or request validation. Covers @stacksjs/validation.
基于 SOC 职业分类
