Release Plan: <title>
Template Front Matter
---
artifact_type: release_plan
slug: <release-plan-slug>
status: draft
index_challenge_ref: <index-challenge-id-or-url>
linear_project_ref: <linear-project-id-or-url>
linear_issue_refs:
- <linear-issue-id-or-url>
linear_milestone_ref: <linear-milestone-id-or-url>
last_validated_at: YYYY-MM-DD
release_note_refs:
- bf-manage-web/docs/release-notes/working/next.public.md
- bf-manage-web/docs/release-notes/working/next.internal.md
- bf-manage-web/docs/release-notes/working/holdback.md
rollout_controls:
- type: workspace_setting
ref: <setting-name-or-path>
---
Summary
- Describe the releasable scope in one sentence.
- State whether this is customer-visible, internal-only, or a staged rollout.
Included Scope
- List the stories or work items covered by this release plan.
- Note the Linear Milestone used for day-to-day planning.
Release Notes
- Link the relevant working release note or weekly published release-note entry governed by this plan.
- State what customers or internal stakeholders should expect to see.
Rollout Controls
- Record the allowed rollout mechanism for shipped scope.
- If rollout is limited, use workspace settings rather than internal iteration flags.
Validation
- State the checks required before the plan can move to
approved.
- Confirm customer-visible scope no longer depends on internal iteration flags.