Write a maintainer playbook for adding a new task input
New generators will appear after launch, and ownership of the invalidation map is currently undocumented.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Technical writing · Build systems
Estimated field mix
- Developer tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional internal tools team maintains eighteen packages. Engineers currently run everything because the affected-package script occasionally misses downstream consumers.
Setup prerequisites
- Create a local six-package fixture with a dependency cycle, shared compiler configuration, and two example changes.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BMONO-101 · Document task inputs beyond package dependencies
- BMONO-102 · Parse workspace manifests without executing package scripts
- BMONO-103 · Handle cycles in the downstream impact graph
- BMONO-104 · Resolve renamed and deleted files against both revisions
- BMONO-106 · Make cache keys include generator versions and relevant environment
- BMONO-105 · Explain why each selected command is necessary
- BMONO-107 · Detect stale plan execution after the worktree changes
- BMONO-108 · Bound parallel commands and stop cleanly on cancellation
- BMONO-109 · Compare selective and full plans over a recorded change corpus
Acceptance criteria
- Show how to declare one generator input and its owner.
- Include the regression case required before selective execution.
- Document diagnosis of unexpected full and empty plans.
Implementation constraints
- Use examples from the implemented planner rather than future capabilities.
Verification to include
- Follow the guide to add a synthetic generator input.
- Verify omission is detected by the comparison procedure.
Deliverables
- Maintainer guide with worked example.
Rollout and recovery
Link the guide from CLI help; withdraw selective defaults if ownership becomes unclear.
Value of the work
For the engineer: Practice graph analysis, reproducible commands, and safe developer-tool failure modes.
For the team: Produce an inspectable CI selection plan that avoids unnecessary work without silently skipping consumers.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.