القائمة
Capture a quick work item from free text. Defaults to type-heuristic; asks if ambiguous. Lands in the inbox (status=captured) for later triage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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-capture |
| description | Capture a quick work item from free text. Defaults to type-heuristic; asks if ambiguous. Lands in the inbox (status=captured) for later triage. |
| argument-hint | <freeform description of work> |
| allowed-tools | ["mcp__squad__squad_new"] |
| disable-model-invocation | true |
You are capturing a quick work item to the squad inbox. The user said:
$ARGS
Look at the text and infer one of: bug, feat, task, chore, debt, bet.
Heuristics (apply in order; first match wins):
bugbugfeatchoredebtbettaskIf you genuinely cannot tell (the text is too vague or matches multiple categories with equal weight), ASK the user to choose between the top 2-3 candidates. Do NOT guess silently.
Once you have a type, call the squad_new MCP tool:
{"type": "<inferred-type>", "title": "<the user's text, trimmed and de-padded>"}
Defaults are correct: status will be captured, the agent's identity is stamped as captured_by. Do NOT pass ready: true — capture-then-triage is the intended flow.
Report back to the user: "captured as : . run squad inbox to see your inbox, or squad accept <ID> when you're ready to claim."