Explain why each selected command is necessary
Maintainers cannot review a large affected set because the tool prints only package names.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- CLI design · Developer experience
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.
Acceptance criteria
- Attach at least one changed input to each selected task.
- Represent transitive paths without unbounded recursion.
- Emit stable JSON and readable plain-text output.
Implementation constraints
- Keep absolute workstation paths out of exported plans.
Verification to include
- Snapshot a direct and a transitive explanation.
- Verify cyclic and missing-owner explanations remain bounded.
Deliverables
- Plan explanation renderer.
Rollout and recovery
Enable explanation output immediately; keep command execution opt-in.
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.