Repository navigation
docs(agents): document the blocked label as a state modifier - #89
Merged
Merged
Conversation
The repository ships a `blocked` label that no document defines, so an issue that cannot be worked until a dependency lands has nowhere canonical to say so. Issue #68 is exactly that shape: fully specified, and waiting on #88. Recorded as a modifier rather than a sixth state. A state answers where an issue sits in triage; `blocked` answers whether work may start, and the two are independent. Keeping them orthogonal leaves the one-state-at-a-time rule intact and leaves the `triage` skill's five-state machine working without knowing the label exists -- as a state it would collide with `ready-for-agent` and erase the difference between not yet specified and specified but waiting. Signed-off-by: Rodrigo França <rodrigo_rjsf@hotmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repository ships a
blockedlabel that no document defines.docs/agents/triage-labels.mdnames five canonical states and three categories;blockedis in neither list, so an issue that is fully specified but cannot be worked until a dependency lands has nowhere canonical to say so.#68 is exactly that shape — its design is settled, and it waits on #88's corpus fixture and spelling survey.
Why a modifier and not a sixth state
A state answers where is this in triage;
blockedanswers may work start. The two are independent — an issue can be fully specified and still unworkable — so the label is documented as orthogonal to the state set.That choice has a concrete consumer consequence. The
triageskill drives a five-state machine and removes the old state label on every transition. A sixth state it does not know would be stripped on the next move, and would collide withready-for-agent, erasing the difference between not yet specified and specified but waiting. As a modifier, the skill's vocabulary is untouched — it neither sets nor clearsblocked, and a human or an agent applies it directly.A blocked-but-specified issue therefore reads
bug+ready-for-agent+blocked, withblockedoverridingready-for-agentin practice.Verification
Prose-only change to one file.
make test-unit,make lintandmake format-checkrun below.https://claude.ai/code/session_01YLQa5TWtgQ2JnhcvPEUyWK