Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Issues and PRDs live in GitHub Issues for `callstack/agent-device`; external PRs

### Triage labels

Follow the issue label workflow in `docs/agents/triage-labels.md`, including `ready-for-agent` and `ready-for-human`.
Follow the issue label workflow in `docs/agents/triage-labels.md`, including `ready-for-agent`.

### Domain docs

Expand Down
6 changes: 2 additions & 4 deletions docs/agents/triage-labels.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,12 @@
# Issue Label Workflow

The skills speak in terms of five canonical triage roles. This file maps those roles to the actual GitHub labels used in this repo.
The skills speak in terms of four canonical triage roles. This file maps those roles to the actual GitHub labels used in this repo.

| Skill role | GitHub label | Meaning |
| --- | --- | --- |
| `needs-triage` | `needs-triage` | New or unreviewed issue; maintainer needs to evaluate it |
| `needs-info` | `needs-info` | Waiting on reporter or external input |
| `ready-for-agent` | `ready-for-agent` | Fully specified, AFK-ready for an agent to pick up |
| `ready-for-human` | `ready-for-human` | Valid work, but needs human implementation or judgment |
| `wontfix` | `wontfix` | Will not be actioned after an explicit maintainer decision |

Default flow:
Expand All @@ -16,5 +15,4 @@ Default flow:
2. Remove `needs-triage` once the issue is understood and valid.
3. Add `needs-info` when reporter or external input is required.
4. Add `ready-for-agent` when the issue is fully specified and can be picked up by an AFK agent with no extra human context.
5. Add `ready-for-human` when the issue is valid but needs human implementation, product judgment, or maintainer ownership.
6. Add `wontfix` only after an explicit maintainer decision.
5. Add `wontfix` only after an explicit maintainer decision.
Loading