Turn change fragments into package-specific release notes
The same release note is pasted into all six packages, even when only one changed. Read small checked-in change fragments and render notes grouped by affected package.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Parsing · Documentation tooling · Deterministic output
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 team maintains six related packages. Release notes, version changes, and tags are copied between a spreadsheet and a terminal; a failed upload recently left two packages ahead of their dependents. The exercise uses temporary repositories and a fake registry.
Setup prerequisites
- Create a temporary Git repository with three related fixture packages.
- Use a local registry double; no publishing credentials are required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Each fragment names existing packages and one supported change category.
- Rendering is deterministic and includes each fragment once per affected package.
- Unknown packages, duplicate fragment IDs, and empty descriptions block generation with file-level errors.
Implementation constraints
- Treat fragment text as plain Markdown content, never executable templates.
- Preserve issue references exactly as supplied.
Verification to include
- Render two overlapping fragments and check package-specific sections.
- Use duplicate IDs and an unknown package to verify the entire notes step fails without writing output.
Deliverables
- Fragment format, examples, and release-note renderer
Rollout and recovery
Generate notes to a preview path initially; switching to committed notes requires the validated plan.
Value of the work
For the engineer: Practice CLI contracts, graph reasoning, filesystem safety, and recovery from partial work.
For the team: Review how an engineer makes release changes inspectable and recoverable before they affect 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.