…Orchestration (#1304) One commit, one deliverable: the `backlog-burndown` Skill and the seating three sibling skills needed for it to work. It was driven as its own feature pull request into `develop` (#1291), reviewed by the PR-hosted reviewers, and merged with CI green and every finding disposed of by one of three routes: fixed, declined on evidence, or deferred behind a filed issue. ## What this promotes **The `backlog-burndown` Skill** (#1291). Working one issue is `drive-pr`'s job. Working a whole backlog is a different problem, and nothing packaged it: parallelism is bounded by file overlap rather than by agent count, the backlog changes every round as reviews file deferral issues, and a prose-heavy repository conflicts on content rather than on syntax. The skill ranks the open issues, groups them so no file is claimed twice, verifies each claim against everything in flight before dispatching, runs at most four workers that each drive their own feature -> develop pull request, opens at most one develop -> main promotion pull request per round for the maintainer to merge, and re-ranks from scratch. It performs no edit of its own and never merges `main`. **Seating in the three skills it drives.** `drive-pr` gains the rule that a dispatched drive takes its target from the brief rather than asking, and that a brief is never itself an authorization. `pr-review-conduct` gains the escalation route for an agent that cannot reach the maintainer. `local-strict-review` states that the reviewer's tier is the one the dispatch can name rather than the one a down-tiered worker runs on. `AGENTS.md` carries the map entry and one Session Scope exception, since a run outlives the single deliverable a session normally covers. ## What this lands with, stated rather than deferred quietly This promotes a known defect list rather than a clean one, which #1291 said explicitly at its own merge. Sixteen review rounds ran over that branch. The later ones hit the churn the new skill's own "Bounding a Prose Group" section describes, where a finding is introduced by the previous round's fix, and the rule it states for that case is to land what is correct and file the remainder. Two rounds' fixes were themselves worse than what they replaced and were reverted there, with the evidence that disproved them filed. Thirty-one issues stand open against this content: #1272 through #1290 filed during the review, and #1293 through #1303 filed after the body above was written. Two are design calls rather than wording and are worth reading before merging this: - **#1290**, the sharpest. The skill's central rule is that no file is claimed by two live groups at once, and in this repository that rule is unsatisfiable, because every canonical-content worker writes `reports/canonical-review.md` and its global counts merge cleanly to a wrong value. - **#1285**, that every worker holds a judgment `AGENTS.md` says never to tier down, since a worker declines review findings by construction. Nothing carries this skill yet, and the remaining defects are contradictions in a procedure document rather than anything executable, which is why filing them beat holding the change. ## Verification Gates run on this merged tree rather than only per pull request: | Gate | Result | | --- | --- | | `unittest discover -s scripts/tests` | 1051 tests, OK | | `scripts/prose_lint.py` | 298 files, clean | | `spec/validate.py` | 22 repos classify cleanly | | `scripts/repo_gate.py --check eol` | 0 issues | | `scripts/repo_gate.py --check eol-coverage` | 0 issues | | `spec/audit.py --selftest` | PASS | | `scripts/build_dist.py --check` | generated distributions current | | `scripts/canonical_review.py check` | no uncovered unit | `spec/audit.py ProjectTemplate` and `repo-config/configure.sh check` were also run live, since CI never runs either. Both report the same single settings finding, `has_projects` live `true` against an expected `false`, plus three README reference findings. All four are pre-existing on `main` and untouched by this promotion, which changes no file under `repo-config/` or `registry/`. The `has_projects` state may well be deliberate given #1292, so it is surfaced here rather than filed as drift. ## Issues closed None. #1291 added new content rather than settling a tracked issue, and the issues that surround it are the ones its own review filed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01HDDDmExAUoCdhbhKBHZwEe  ## Summary by CodeRabbit - **New Features** - Added a backlog-burndown workflow for ranking issues, coordinating parallel work, managing pull requests, and preparing promotions. - Added the new workflow to the skills plugin. - **Documentation** - Clarified authorization, escalation, review, promotion, and maintainer-approval procedures. - Documented how dispatched work handles blocked decisions and unavailable reviewers. - **Reports** - Updated review records and coverage reporting to include the new and revised guidance.

Link all fleet repos to the "Fleet Engineering" project #1292

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions