菜单
Interactively define a new project from scratch — captures the core idea, architecture, tech stack, non-goals, constraints, and team composition into a PROJECT.md source-of-truth doc. Run this before /new-team-phase or /team-kickoff.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interactively scaffold a new team-kickoff phase config YAML. Use when the user wants to plan a new phase but doesn't have a config file yet.
Execute approved plan docs by spawning teammates to write actual code. Takes the same phase config YAML used by /team-kickoff. Each teammate reads their approved plan doc and writes the code files described in it, then self-verifies with build and test commands.
Scaffold a complete code project — generates PROJECT.md and phase kickoff YAMLs from a few questions. Analyzes project complexity to decide phases, teammate roles, and focus areas automatically. Run this to go from idea to ready-to-kickoff in seconds.
Execute approved plan docs by re-spawning teammates to write full deliverables. Takes the same phase config YAML used by /team-kickoff. Each teammate reads their approved plan doc and produces the final detailed content.
Spawn a multi-agent planning team from a phase config YAML. Use when the user wants to kick off a new planning phase with multiple specialized teammates, each writing a dedicated plan doc. Each teammate stays in PLAN MODE and follows the master plan template verbatim.
Show project progress — what's done, what's next, and what to kick off. Reads PROJECT.state.yaml to give a status report across all work streams.
| name | init-team-project |
| description | Interactively define a new project from scratch — captures the core idea, architecture, tech stack, non-goals, constraints, and team composition into a PROJECT.md source-of-truth doc. Run this before /new-team-phase or /team-kickoff. |
| disable-model-invocation | false |
Help the user create a PROJECT.md that serves as the foundational source of truth for all future phase planning.
Ask all at once (do not ask one at a time):
Once the user answers, produce the following document. Write it to PROJECT.md at the project root (confirm path before writing).
# <Project Name>
> <one-line description>
---
## Problem & Motivation
<problem / motivation>
---
## Definition of Done
<what "finished" looks like — capabilities unlocked, user outcomes, success state>
---
## Key Components
<bulleted list of major system components with a one-line description each>
---
## Tech Stack
<language, frameworks, infra, must-use tools>
---
## Non-Goals
<what is explicitly out of scope>
---
## Constraints
<hard constraints, or "None">
---
## Team
| Role | Focus |
|------|-------|
| <role> | <focus> |
...
---
## Usage in Phase Planning
This file is the source of truth for all planning phases.
List it as the first dependency in every phase config:
\`\`\`yaml
dependencies:
- PROJECT.md
- <other docs>
\`\`\`
Every teammate spawned by `/team-kickoff` should read this file before writing their plan.
Ask: "Should I save this to PROJECT.md?" (suggest project root as default, but let user override).
If yes, write the file. Then print:
PROJECT.md saved. Next steps:
1. Run /new-team-phase to scaffold your first planning phase.
(PROJECT.md will be pre-suggested as a dependency.)
This will also create PROJECT.state.yaml for progress tracking.
2. Or if you already have a phase config:
/team-kickoff path/to/config.yaml
3. Check progress any time with:
/where-are-we
Tip: list PROJECT.md as the first dependency in every phase config
so all teammates share the same project foundation.