Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

squad-capture

Étoiles0

Forks0

Mis à jour26 avril 2026 à 20:41

Capture a quick work item from free text. Defaults to type-heuristic; asks if ambiguous. Lands in the inbox (status=captured) for later triage.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

zsiec

zsiec/squad

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

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

Step 1: Infer the type

Look at the text and infer one of: bug, feat, task, chore, debt, bet.

Heuristics (apply in order; first match wins):

Contains "bug", "broken", "crash", "error", "fail", "regression" → bug
Starts with "fix", "repair", "patch" → bug
Starts with "add", "support", "enable", "let me", "i want" → feat
Contains "refactor", "cleanup", "tidy", "rename" → chore
Contains "tech debt", "legacy", "duplication", "extract" → debt
Contains "experiment", "spike", "see if", "find out" → bet
Otherwise → task

If 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.

Step 2: Call squad_new

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.

Step 3: Confirm

Report back to the user: "captured as : . run squad inbox to see your inbox, or squad accept <ID> when you're ready to claim."

Plus depuis ce dépôt

même dépôt

squad-evidence-requirement

zsiec/squad

Every "tests pass" / "build green" / "feature works" claim needs the actual command output pasted into the conversation. Bare assertions are worth zero.

2026-04-280

squad-loop

zsiec/squad

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.

2026-04-280

squad-chat-cadence

zsiec/squad

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.

2026-04-280

squad-tick

zsiec/squad

Tick the squad team — surface mentions and file conflicts. Address mentions BEFORE continuing other work.

2026-04-280

squad-handoff

zsiec/squad

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.

2026-04-270

squad-intake

zsiec/squad

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.

2026-04-270

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

Step 1: Infer the type

Look at the text and infer one of: bug, feat, task, chore, debt, bet.

Heuristics (apply in order; first match wins):

Contains "bug", "broken", "crash", "error", "fail", "regression" → bug
Starts with "fix", "repair", "patch" → bug
Starts with "add", "support", "enable", "let me", "i want" → feat
Contains "refactor", "cleanup", "tidy", "rename" → chore
Contains "tech debt", "legacy", "duplication", "extract" → debt
Contains "experiment", "spike", "see if", "find out" → bet
Otherwise → task

If 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.

Step 2: Call squad_new

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.

Step 3: Confirm

Report back to the user: "captured as : . run squad inbox to see your inbox, or squad accept <ID> when you're ready to claim."