菜单
File a new item. Runs squad new with type and title, then injects the standard item template body for you to fill in.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Every "tests pass" / "build green" / "feature works" claim needs the actual command output pasted into the conversation. Bare assertions are worth zero.
The operating loop every session follows — register, tick, pick, work, checkpoint, test, review, commit, close. Use whenever you start or resume work on a squad-managed repo.
Post often, post small, post honestly. The team needs visibility into your non-obvious state — not a change log. Use the typed verbs (thinking / milestone / stuck / fyi / ask) so peers can route attention.
Tick the squad team — surface mentions and file conflicts. Address mentions BEFORE continuing other work.
Before signing off — whether you finished an item or stopped mid-flight — post a 3-bullet summary. Shipped, in flight / queued, surprised by. Three bullets, no ceremony.
Run a structured intake interview with the user — open a session, ask one focused question per turn, draft the bundle, confirm with the user, then commit. Supports green-field (mode=new) and refine-mode (mode=refine) flows.
| name | squad-file |
| description | File a new item. Runs squad new with type and title, then injects the standard item template body for you to fill in. |
| argument-hint | <type> "<title>" |
| allowed-tools | ["Bash","Edit"] |
| paths | [".squad/items/**"] |
| disable-model-invocation | true |
You are filing a new item. Run:
squad new $ARGS
This creates a new item file under .squad/items/ with frontmatter populated. Open the file and fill in the body using this template:
## Problem
<What is wrong / what does not exist. 1–3 sentences.>
## Context
<Why this matters. Where in the codebase it lives. What has been tried. Link to upstream specs if relevant.>
## Acceptance criteria
- [ ] Specific, testable thing 1
- [ ] Specific, testable thing 2
- [ ] (For bugs) A failing test exists; it now passes.
## Notes
<Optional design notes. Trade-offs considered. Pointers to related items.>
Risk classification reminder: bump risk: from low if the change touches sensitive paths defined in .squad/config.yaml. For risk: high items where rollback is non-trivial (schema migrations, multi-tier cutovers, anything git revert alone does not fully reverse), add a ## Rollback plan section before coding.
If this item is P0 or P1, add it to the "Ready" section of STATUS.md.
Commit:
git add .squad/items/<new-file>.md
git commit -m "docs: add <ID> <title>"
(No PM-trace IDs in the commit message body — the filename carries the ID.)