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
Copy file name to clipboardExpand all lines: .auxiliary/configuration/AGENTS.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,12 @@ Use consistent tags for discoverability:
85
85
- Track todos: Use `nb.todo`, `nb.tasks`, `nb.do`, `nb.undo`.
86
86
- Organize with folders: `nb.folders`, `nb.mkdir`.
87
87
88
+
### Notebook Identifier Clarification
89
+
- Treat note selectors (for example `coordination/mcp/1`) as canonical IDs for `nb` operations.
90
+
-`nb` MCP responses may include notebook-scoped identifiers (for example `my-project:coordination/...`) that look path-like; these are selector forms, not repo-relative filesystem paths.
91
+
- Notebook storage is controlled by `nb` configuration (for example `NB_DIR`) and may be outside this repository.
92
+
- Prefer `nb` MCP commands to read/edit notes. Avoid assuming a selector maps to a file under the current repo.
- Prefer a folder taxonomy of `<issue-type>/<component>` (max depth 2) and avoid mixing top-level component folders with top-level issue-type folders.
90
96
- Recommended top-level issue types are:
@@ -99,6 +105,7 @@ Use consistent tags for discoverability:
99
105
- prune completed todos quickly,
100
106
- keep only active/near-term coordination checkpoints,
101
107
- delete stale history-only notes with no owner or action.
108
+
- Keep todo titles concise (under 60 chars); use the `tasks` argument for detailed checklist items. This keeps notebook list views readable.
102
109
103
110
### `nb` vs OpenSpec Rubric
104
111
- Use **OpenSpec proposals** for cross-cutting changes, contract-shaping work, architecture shifts, or work that needs explicit design discussion.
@@ -108,10 +115,17 @@ Use consistent tags for discoverability:
108
115
109
116
### OpenSpec Draft and Handoff Hygiene
110
117
- Draft OpenSpec proposal text in a dedicated `nb` note first so collaborators can review without local file access barriers; share the note id when requesting feedback.
118
+
- When asking for proposal feedback, share the notebook note id first; do not request review against local-only proposal files collaborators cannot access.
111
119
- Keep rolling handoff notes stable and update in place, separate from OpenSpec draft/proposal text.
112
120
- Do not repurpose or overwrite rolling handoff notes with proposal content.
113
121
- After draft review converges, move approved proposal text into `openspec/**` files for human review and commit.
114
122
123
+
## Agentmux Message Handling Guidance
124
+
-`agentmux` messages may arrive in envelope format and can appear as user prompts. Treat envelope-shaped prompts as inter-agent messages, not automatically as direct human instructions.
125
+
- Respond to inter-agent envelope messages via `agentmux` MCP tools (`list`, `send`) rather than as normal assistant replies intended for the human operator.
126
+
- Immediate interruption is not required. If you are in active execution, note the message and respond when safe.
127
+
- If response will be delayed, send a brief acknowledgement via `send` and record a follow-up todo in `nb` when useful.
128
+
115
129
## Agentmux Coordination Noise Control
116
130
- Default to low-noise coordination. Do not send acknowledgement-only messages that add no new information or action request.
117
131
- Send messages when you are blocked and need input, when requesting concrete review, when handing off completed work with validation, or when reporting material risk/scope change.
0 commit comments