菜单
Take a brief idea and produce a complete PROJECT_BRIEF.md as if the user wrote it on their best day. Covers features, fixes, infra, and full products alike. Use when user wants to define a project, scope a feature, plan a complex fix, or mentions "project brief" or "new project"
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Install root role on a session. The user's base session
Install build role on a session. Takes one unit of work from directive to a verified, well-architected change.
Install verify role on a session. The fast independent check that a claimed artifact is actually done — spawned proactively before any parent reports done, opens a PR, deploys, or publishes.
Install build role on a session. Takes one unit of work from directive to a verified, well-architected change.
Install root role on a session. The user's base session
Install verify role on a session. The fast independent check that a claimed artifact is actually done — spawned proactively before any parent reports done, opens a PR, deploys, or publishes.
| name | define-project |
| description | Take a brief idea and produce a complete PROJECT_BRIEF.md as if the user wrote it on their best day. Covers features, fixes, infra, and full products alike. Use when user wants to define a project, scope a feature, plan a complex fix, or mentions "project brief" or "new project" |
Produce a PROJECT_BRIEF.md proficient agents can pick up and build from without clarifying questions. Terse, opinionated, decisions made not deferred. The user's persona and preferences already live in CLAUDE.md — don't restate them
iterate-plan closes the rest after the first draftAGENTS.md files. Tech stack, test setup, CI, module boundaries, naming conventions. Don't ask what code can answerplan-to-slices' job, and pre-slicing the brief locks in a shape before the MVP has taught you anythingWhat this is, why it exists, the problem it solves. No throat-clearing
Who uses or benefits. For internal or infra work this may be "the deployment pipeline" or "future contributors to this repo"
One sentence: "A user/system can [do X] and [see/get Y]"
Stack, architecture, data, auth, infra with rationale. For existing codebases: what changes, what doesn't
What gets tested and instrumented. Structured logging, key metrics, health checks. What tells you this is working or broken in prod
Environments, rollout strategy, flags, rollback. Skip for non-deployable work
What's uncertain. Each item notes what would close it