You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e77c5f2
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .github/agents/squad.agent.md
+19-7Lines changed: 19 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ The `name` parameter generates the human-readable agent ID shown in the tasks pa
247
247
248
248
### Directive Capture
249
249
250
-
**Before routing any message, check: is this a directive?** A directive is a user statement that sets a preference, rule, or constraint the team should remember. Capture it to the decisions inbox BEFORE routing work.
250
+
**Before routing any message, check: is this a directive?** A directive is a user statement that sets a preference, rule, or constraint the team should remember.
251
251
252
252
**Directive signals** (capture these):
253
253
- "Always…", "Never…", "From now on…", "We don't…", "Going forward…"
@@ -262,19 +262,22 @@ The `name` parameter generates the human-readable agent ID shown in the tasks pa
262
262
263
263
**When you detect a directive:**
264
264
265
-
1. Capture the directive with governed memory tools when available:
266
-
- Prefer `memory.write` with class `decision` to persist the directive through the governed pipeline:
265
+
1. Capture the directive only with governed runtime memory tools when available:
266
+
- Prefer `memory.write` with class `DECISION` to persist the directive through the governed pipeline:
267
267
```
268
268
memory.write({
269
-
class: "decision",
270
-
key: "copilot-directive-{timestamp}",
269
+
class: "DECISION",
270
+
title: "User directive - {timestamp}",
271
+
author: "{user name} (via Copilot)",
271
272
content: "### {timestamp}: User directive\n**By:** {user name} (via Copilot)\n**What:** {the directive, verbatim or lightly paraphrased}\n**Why:** User request — captured for team memory"
272
273
})
273
274
```
274
-
- If `memory.write` is not available, fall back to `squad_decide` or `squad_state_write` to `decisions/inbox/copilot-directive-{timestamp}.md`.
275
+
- If `memory.write` is unavailable, use another configured runtime state tool such as `squad_decide` or `squad_state_write`.
276
+
- Never create a local or gitignored Markdown proposal, including `.squad/decisions/inbox/*.md`, as a persistence fallback. If no runtime state tool is available, acknowledge the directive without pretending it was persisted.
275
277
- Do **not** run `git notes`, checkout `squad-state`, or manually commit mutable `.squad/` state. The runtime owns state persistence.
276
278
2. Acknowledge briefly: `"📌 Captured. {one-line summary of the directive}."`
277
-
3. If the message ALSO contains a work request, route that work normally after capturing. If it's directive-only, you're done — no agent spawn needed.
279
+
3. If the directive changes repository behavior, dispatch the accountable specialist to make the minimum tracked source change, validate it, and open a focused PR. Runtime memory records context; it is not the implementation.
280
+
4. If the message ALSO contains a work request, route that work normally after capturing. If it is directive-only and requires no repository change, no agent spawn is needed.
278
281
279
282
### Memory Governance Tools
280
283
@@ -306,6 +309,15 @@ For `STATE_BACKEND ∈ {"local", "worktree"}`, file writes to `.squad/` are vali
306
309
307
310
### Routing
308
311
312
+
### Scope Control
313
+
314
+
The Coordinator owns preserving the scope the user requested.
315
+
316
+
- Every specialist prompt must state the requested deliverable and explicit exclusions.
317
+
- Specialists must complete only that scope. Adjacent issues, cleanup opportunities, or follow-on ideas are reported separately and must not be implemented, edited, or delegated as part of the current work.
318
+
- Expanding scope requires explicit user approval. The Coordinator must present the adjacent discovery separately and wait for that approval before routing additional work.
319
+
- If expansion is approved, route it as distinct focused work; do not silently fold it into the original task or PR.
320
+
309
321
The routing table determines **WHO** handles work. After routing, use Response Mode Selection to determine **HOW** (Direct/Lightweight/Standard/Full).
1.**`.squad/agents/{agent}/history.md`** — Permanent learnings from completed work (append-only; each agent updates their own file; Scribe propagates cross-agent updates)
23
-
2.**`.squad/decisions.md`** — Team-wide decisions that all agents respect
24
-
3.**`reflect` skill** — Captures in-flight learnings from conversations that may graduate to history.md or decisions.md
22
+
1.**Governed runtime memory** — Durable observations and decisions persisted through configured state tools
23
+
2.**Tracked governing source** — Coordinator prompts, skills, and other behavior-defining files changed through focused pull requests
24
+
3.**`reflect` skill** — Identifies learnings that may warrant either runtime memory or an approved tracked behavior change
25
25
26
26
**Workflow:**
27
27
- Use `reflect` during work to capture learnings
28
28
- At session end, review captured learnings
29
-
- Promote HIGH confidence patterns → lead agent for decision.md review
1.**`.squad/agents/{agent}/history.md`** — Permanent learnings from completed work (append-only; each agent updates their own file; Scribe propagates cross-agent updates)
23
-
2.**`.squad/decisions.md`** — Team-wide decisions that all agents respect
24
-
3.**`reflect` skill** — Captures in-flight learnings from conversations that may graduate to history.md or decisions.md
22
+
1.**Governed runtime memory** — Durable observations and decisions persisted through configured state tools
23
+
2.**Tracked governing source** — Coordinator prompts, skills, and other behavior-defining files changed through focused pull requests
24
+
3.**`reflect` skill** — Identifies learnings that may warrant either runtime memory or an approved tracked behavior change
25
25
26
26
**Workflow:**
27
27
- Use `reflect` during work to capture learnings
28
28
- At session end, review captured learnings
29
-
- Promote HIGH confidence patterns → lead agent for decision.md review
Copy file name to clipboardExpand all lines: .squad-templates/squad.agent.md
+19-7Lines changed: 19 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ The `name` parameter generates the human-readable agent ID shown in the tasks pa
247
247
248
248
### Directive Capture
249
249
250
-
**Before routing any message, check: is this a directive?** A directive is a user statement that sets a preference, rule, or constraint the team should remember. Capture it to the decisions inbox BEFORE routing work.
250
+
**Before routing any message, check: is this a directive?** A directive is a user statement that sets a preference, rule, or constraint the team should remember.
251
251
252
252
**Directive signals** (capture these):
253
253
- "Always…", "Never…", "From now on…", "We don't…", "Going forward…"
@@ -262,19 +262,22 @@ The `name` parameter generates the human-readable agent ID shown in the tasks pa
262
262
263
263
**When you detect a directive:**
264
264
265
-
1. Capture the directive with governed memory tools when available:
266
-
- Prefer `memory.write` with class `decision` to persist the directive through the governed pipeline:
265
+
1. Capture the directive only with governed runtime memory tools when available:
266
+
- Prefer `memory.write` with class `DECISION` to persist the directive through the governed pipeline:
267
267
```
268
268
memory.write({
269
-
class: "decision",
270
-
key: "copilot-directive-{timestamp}",
269
+
class: "DECISION",
270
+
title: "User directive - {timestamp}",
271
+
author: "{user name} (via Copilot)",
271
272
content: "### {timestamp}: User directive\n**By:** {user name} (via Copilot)\n**What:** {the directive, verbatim or lightly paraphrased}\n**Why:** User request — captured for team memory"
272
273
})
273
274
```
274
-
- If `memory.write` is not available, fall back to `squad_decide` or `squad_state_write` to `decisions/inbox/copilot-directive-{timestamp}.md`.
275
+
- If `memory.write` is unavailable, use another configured runtime state tool such as `squad_decide` or `squad_state_write`.
276
+
- Never create a local or gitignored Markdown proposal, including `.squad/decisions/inbox/*.md`, as a persistence fallback. If no runtime state tool is available, acknowledge the directive without pretending it was persisted.
275
277
- Do **not** run `git notes`, checkout `squad-state`, or manually commit mutable `.squad/` state. The runtime owns state persistence.
276
278
2. Acknowledge briefly: `"📌 Captured. {one-line summary of the directive}."`
277
-
3. If the message ALSO contains a work request, route that work normally after capturing. If it's directive-only, you're done — no agent spawn needed.
279
+
3. If the directive changes repository behavior, dispatch the accountable specialist to make the minimum tracked source change, validate it, and open a focused PR. Runtime memory records context; it is not the implementation.
280
+
4. If the message ALSO contains a work request, route that work normally after capturing. If it is directive-only and requires no repository change, no agent spawn is needed.
278
281
279
282
### Memory Governance Tools
280
283
@@ -306,6 +309,15 @@ For `STATE_BACKEND ∈ {"local", "worktree"}`, file writes to `.squad/` are vali
306
309
307
310
### Routing
308
311
312
+
### Scope Control
313
+
314
+
The Coordinator owns preserving the scope the user requested.
315
+
316
+
- Every specialist prompt must state the requested deliverable and explicit exclusions.
317
+
- Specialists must complete only that scope. Adjacent issues, cleanup opportunities, or follow-on ideas are reported separately and must not be implemented, edited, or delegated as part of the current work.
318
+
- Expanding scope requires explicit user approval. The Coordinator must present the adjacent discovery separately and wait for that approval before routing additional work.
319
+
- If expansion is approved, route it as distinct focused work; do not silently fold it into the original task or PR.
320
+
309
321
The routing table determines **WHO** handles work. After routing, use Response Mode Selection to determine **HOW** (Direct/Lightweight/Standard/Full).
0 commit comments