PR-ready specifications
Implementation packages a Claude thread (or a person) can pick up and build as one pull request. Each follows the same sixteen sections, from the business problem to the Definition of Done, and names its backlog item in the product backlog.
None of these is approved. A package is built only after the product owner moves its backlog item to Approved. Packages exist only for items no specialist program owns; owned items are specified by their programs (see the backlog's ownership table).
Recommended execution sequence#
| Order | Package | Priority | Effort | Why this position |
|---|---|---|---|---|
| 1 | PB-002 Tenant smoke test | P0 | M | Every other verification claim waits on it; needs the maintainer's non-production workspace |
| 2 | PB-071 Rust tests in CI | P1 required | S | Makes later shell changes safe; PB-008 and PB-072 depend on it |
| 3 | PB-010 Security and network docs | P1 required | S | IT reviewers read these first; docs only |
| 4 | PB-078 Preview tags match the docs | P1 required | S | Lets organizations hide what isn't proven |
| 5 | PB-013 Local-parity defects | P1 required | M | Removes wrong answers in local execution |
| 6 | PB-051 Fabric client resilience | P1 required | S | Fewer failed actions on a live tenant; informs PB-002 reruns |
| 7 | PB-043 Cancel a Fabric run | P2 | S | Stops runaway capacity use from where people watch runs |
| 8 | PB-077 User and agent docs | P2 | S | Docs only |
| 9 | PB-018 Publish by item id | P2 | S | Prevents duplicate Fabric notebooks |
| 10 | PB-044 Agent queue prune and requeue | P2 | S | Agent hygiene before wider agent use |
Packages 2 to 10 touch different files and can run in parallel threads, except that PB-010 and PB-077 both edit docs and should merge one after the other.
On 2026-10-17 the Codebase audit and hardening thread took over three of these: PB-071 (as HD-011), PB-010 (as HD-009, a P0 there) and PB-051 (as HD-039 and HD-051). Their packages stay here as input for that thread and are not built separately.
Package template#
Every package has these sections:
- PR title and ID
- Business problem
- Current verified behavior (with file references and what was observed versus read)
- Desired behavior
- In scope and out of scope
- Architecture and files
- Functional requirements
- Nonfunctional requirements
- Dependencies
- Security and compatibility
- Acceptance criteria
- Unit and integration tests
- Manual verification
- Documentation
- Rollback
- Definition of Done
After a package's PR merges, it goes through the implementation review before its backlog item can be Accepted.
Need a hand?
Find a fix in troubleshooting, or share a reproducible issue with the community.
Get support ↗Improve this guide on GitHub ↗