Skip to content

Improve decision-triage From Its First Full Run - #3760

Merged
ptr727 merged 6 commits into
developfrom
decision-triage-first-run-3759
Nov 1, 2026
Merged

ptr727 merged 6 commits into
developfrom
decision-triage-first-run-3759

Conversation

@ptr727

@ptr727 ptr727 commented Nov 1, 2026 •

Copy link
Copy Markdown
Owner

Implements the lessons from the first full decision-triage run (#3759), items 1-7. Items 6 and 7 follow the maintainer's answer comment on the issue.

Changes

  • Research cost (item 1). Researchers take topic clusters of five or six questions. Step 3 states the researcher count and a token estimate before dispatching.
  • Comment weighting (item 2). The researcher brief says to read every comment newest last. A later maintainer or evidence comment outranks the body's design, and a tool's or bot's own statement of its behavior counts as evidence.
  • OVERTAKEN (item 3). The classifier runs a cheap history check (git log origin/main, the state of child issues, later decision comments) and can return OVERTAKEN. A fix that is only on develop is HELD awaiting promotion. Queued decision issues get the same check. A new step 6 offers to close overtaken issues.
  • Public output and write bound (item 4). The brief says researcher output is posted publicly and may cite only the repository, its history, and GitHub state. Each subagent gets a scratch directory of its own and writes nothing to the repository or GitHub.
  • Coupled questions (item 5). Questions linked by a BLOCKS line, or whose fixes edit the same section, go in one prompt within the age order, with a split rule.
  • deferred label (item 6). Declared in repo-config/labels.json and described in repo-config/README.md "Labels". decision-triage applies it on a "not yet" answer. The classifier and backlog-burndown skip it and report it by count.
  • Agent-safety approval (item 7). A maintainer-sourced approval comment lets an attended run implement and drive an agent-safety edit. The merge still waits on a per-PR go-ahead given after reading the diff. backlog-burndown's merge grant is carved out for these PRs, and away mode still holds every such edit.
  • Regenerated .github/skills/ and .claude-plugin/ with build_dist.py.

Local Review

Three frontier passes ran. Two edit rounds fixed 13 of round 1's 15 findings and 4 of round 2's 5. Findings declined with evidence:

  • Re-reading each deferred condition every round: the maintainer's answer specifies skip and count-only reporting.
  • Holding a promotion on a "not yet" decision: that hold is what "not yet" means.
  • A GOVERNANCE wording clash with "deferred": GOVERNANCE's "asked once and deferred" means the asking was put off, a case step 7 keeps labelled.

A follow-up push with its own budget fixed the final pass's three introduced findings:

  1. A gated agent-safety group ends as stopped on a maintainer-only question, so "Raising a Blocked Question" asks for the merge go-ahead. A resumed worker's brief then carries that go-ahead for the pull request.
  2. The classifier brief states how a kept-open comment reads.
  3. A queued decision HELD awaiting promotion leaves the queue and stays open. The first triage after the promotion then returns it as OVERTAKEN.

The pass over 7751a2d found nothing (COUNT 0) and is recorded.

Pre-existing findings, filed

After Merge

Refs #3759

🤖 Generated with Claude Code

ptr727 and others added 3 commits November 1, 2026 09:00
Cluster research by topic and state its cost before dispatching. Add a
classifier OVERTAKEN line backed by a cheap history check, and offer to
close overtaken issues that hold nothing else. Brief researchers to read
every comment newest last, that their output is posted publicly, and to
write only to a named scratch directory. Ask questions that settle each
other in the same prompt.

Add a deferred label for a decision answered "not yet", applied by
decision-triage and counted but not ranked by backlog-burndown. Let a
recorded approval from an account with write access clear the
agent-safety hold for an attended run, with the merge still needing the
maintainer present and away mode still holding every such edit.

Refs #3759

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Key each researched question to its issue number, give queued decisions
the history check, read that check against origin/main, and hold a
develop-only fix as awaiting promotion. Name a maintainer-sourced
approval and keep an agent-safety merge outside any standing merge
go-ahead. State when deferred comes off, give each subagent its own
scratch directory, and narrow and split coupled-question groups.

Refs #3759

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
State in backlog-burndown's authorization that the run's merge grant
does not reach an agent-safety pull request, and brief its worker not
to merge. Exclude HELD queued decisions from research, count a fix as
overtaking only once it is on origin/main, define what a kept-open
comment means to a later history check, and let a session lift
deferred alone only on checkable state.

Refs #3759

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ptr727 ptr727 added enhancement New feature or request skills Agent skill labels Nov 1, 2026
Copilot AI lite review requested due to automatic review settings November 1, 2026 17:11
@ptr727 ptr727 added enhancement New feature or request skills Agent skill labels Nov 1, 2026
@coderabbitai

coderabbitai Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Several active documentation issues remain, including an unsafe attended dispatch path, an undefined worker outcome, and incomplete decision-triage transitions that could leave work blocked or misclassified.

5 open issues
What changed in this PR

This pull request improves the decision-triage and backlog-burndown workflows based on their first full run, adding deferred decisions, history checks, clustered research, coupled-question handling, and agent-safety approval gates. It also regenerates the distributed skill files and source digests.

Changes:

  • Adds and documents the deferred label and its triage/backlog behavior.
  • Adds OVERTAKEN/HELD handling, improved evidence weighting, research constraints, and coupled-question ordering.
  • Adds agent-safety approval and merge restrictions.
  • Regenerates GitHub, Claude, and canonical skill distributions.

Five unresolved review findings remain, including an attended-path agent-safety bypass, incomplete gated and HELD outcomes, missing classifier handling for partial overtakes, and unclear overtaken-issue wording.

This pull request requires changes.

File Description
repo-config/​README.md Documents the new deferred label and backlog behavior.
repo-config/​labels.json Declares the fleet-wide deferred label.
.github/​skills/​decision-triage/​SKILL.md Regenerated GitHub Copilot decision-triage distribution.
.github/​skills/​backlog-burndown/​SKILL.md Regenerated GitHub Copilot backlog-burndown distribution.
.claude-plugin/​fleet-skills/​skills/​decision-triage/​SKILL.md Regenerated Claude decision-triage distribution.
.claude-plugin/​fleet-skills/​skills/​backlog-burndown/​SKILL.md Regenerated Claude backlog-burndown distribution.
.claude-plugin/​fleet-skills/​.source-digests/​decision-triage Updates the decision-triage source digest.
.claude-plugin/​fleet-skills/​.source-digests/​backlog-burndown Updates the backlog-burndown source digest.
.agents/​skills/​decision-triage/​SKILL.md Canonical decision-triage procedure and brief updates.
.agents/​skills/​backlog-burndown/​SKILL.md Canonical backlog and agent-safety workflow updates.

Review effort: Lite

Comment thread .agents/skills/decision-triage/SKILL.md Resolved
Comment thread .agents/skills/decision-triage/SKILL.md Resolved
Comment thread .agents/skills/decision-triage/SKILL.md Resolved
@codecov

codecov Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.31%. Comparing base (4b7c352) to head (af43ea2).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #3760   +/-   ##
========================================
  Coverage    82.31%   82.31%           
========================================
  Files           28       28           
  Lines         9438     9438           
========================================
  Hits          7769     7769           
  Misses        1669     1669           
Flag Coverage Δ
python-3.13 82.31% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

ptr727 and others added 2 commits November 1, 2026 09:23
Name a gated agent-safety group as stopped on a maintainer-only
question, carry step 6's kept-open meaning into the classifier brief,
and take a queued decision held awaiting promotion out of the queue
while it stays open for the promotion to close.

Refs #3759

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Say that a held decision returns as OVERTAKEN at the first triage after
its promotion, and that a resumed agent-safety worker's brief carries the
maintainer's per-PR go-ahead in place of the no-merge line.

Refs #3759

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ptr727

ptr727 commented Nov 1, 2026

Copy link
Copy Markdown
Owner Author

A recorded local strict-review pass covers head 7751a2d1baceac4621b969c99d38da15fbcf025b, the content this pull request carries at that commit against develop, and it recorded 0 findings.

Refs #3759

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ptr727

ptr727 commented Nov 1, 2026

Copy link
Copy Markdown
Owner Author

A recorded local strict-review pass covers head af43ea2eea7a58820d68c87bd44e151e28b60c38, the content this pull request carries at that commit against develop, and it recorded 0 findings.

@ptr727
ptr727 merged commit c7cc453 into develop Nov 1, 2026
13 checks passed
@ptr727
ptr727 deleted the decision-triage-first-run-3759 branch November 1, 2026 17:38
ptr727 added a commit that referenced this pull request Nov 1, 2026
…Fetch Before Its History Check (#3762)

Promotes the changes merged into `develop` since promotion #3736 to
`main`.

- [#3760](#3760) improves
`decision-triage` from its first full run:
- Researchers take topic clusters, and step 3 states the researcher
count and a token estimate before dispatching.
- The researcher brief reads every comment newest last, says its output
is posted publicly, and bounds writes to a scratch directory of its own.
- The classifier can return `OVERTAKEN` after a cheap history check, and
a new step offers to close overtaken issues.
  - Coupled questions are asked in one prompt.
- A new `deferred` label marks a "not yet" answer, which the classifier
and `backlog-burndown` skip and report by count.
- A recorded maintainer approval lets an attended run implement an
agent-safety edit, with the merge still waiting on a per-PR go-ahead.
- [#3763](#3763) has the
triaging session fetch `main` and `develop` once before dispatching the
history check and the researchers, and stop if the fetch fails. The
subagents read the full remote-tracking refs and fetch nothing. It
answers this promotion's first review round.

After the release, the maintainer runs `repo-config/configure.sh apply
ptr727/ProjectTemplate` to create the `deferred` label, then labels
#781, #1464 and #2174 `deferred`, per #3760's "After Merge".

Deferred review findings: #3761 (an attended `backlog-burndown` run
applies no agent-safety hold to an unapproved issue).

Fixes #3759

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request skills Agent skill

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants