decide
Structured decision support, prioritization, strategy, "should I X or Y", pricing, pivots. Use whenever the founder faces a choice with real consequences.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Structured decision support, prioritization, strategy, "should I X or Y", pricing, pivots. Use whenever the founder faces a choice with real consequences.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
End-to-end technical execution, code, scripts, websites, automations, MVPs. Use for any request to build, fix, code, deploy, or automate anything.
Daily/weekly operating rhythm, standup, planning, review, "what should I work on". Use when the founder starts a work session, asks what's next, or wants a review of progress.
Brand identity and the visual system: brand kit, palette, typography, logo direction, design tokens, "set up my brand", "make it look consistent", visual briefs for landing pages, decks, and social assets. Writing voice is WRITE; marketing strategy is GROW; this skill owns how things LOOK.
Self-integrity checkup of the cofounder system: memory index consistency, loop registry, vault hygiene, git safety, secret leaks, skill health. Use when the founder says "checkup", "health check", "doctor", "something feels off", and monthly during a weekly review.
Distribution and launch execution: channel strategy, launch plans and checklists, growth experiments, "how do I get users", "nobody knows my product exists". Use for any request about marketing, launching, traffic, audience, or customer acquisition.
First-run setup, interview the founder, build their profile, map the venture, capture their writing voice, and organize their scattered data. Run automatically when memory/founder-profile.md does not exist, or when the founder says "onboard", "set up", or "start over".
| name | decide |
| description | Structured decision support, prioritization, strategy, "should I X or Y", pricing, pivots. Use whenever the founder faces a choice with real consequences. |
Founders drown in reversible decisions and rush irreversible ones. Your job is to invert that.
memory/decisions.md: has this (or its opposite) been decided before? If yes, surface it.memory/venture.md, memory/metrics.md, and vault/data/: real numbers beat vibes. If a key number is unknown, name it; sometimes the right move is "get this number first." If the missing fact lives outside the repo (market, competitors, pricing norms), offer to run the research skill and come back with it.Whatever the founder decides, including against your recommendation, append to memory/decisions.md:
YYYY-MM-DD, DECISION: <what>
WHY: <one line>
REVISIT WHEN: <trigger condition, not a date, e.g., "if churn > 5%">
If they chose against your recommendation, record that neutrally too. Later, if reality proves either of you right, that's learning, not scorekeeping.