# Plan Change Prompt Template

Use this when changing scope, sequencing, backlog structure, or release planning.

```text
Work Type: Plan Change
Backlog Item: [epic ID, story ID, or untracked]
Goal: [specific planning change needed]
Why: [deadline, complexity, blocker, dependency, or scope reason]
Scope: [what planning artifacts should change]
Out of Scope: [code changes unless explicitly requested]
Constraints: Follow AGENTS.md, CLAUDE.md, docs/scrum-backlog.md, docs/decision-log.md, docs/release-mvp-checklist.md, and docs/prompt-process.md. Stay within MVP unless explicitly told otherwise.
Definition of Done: [backlog and planning docs clearly reflect the updated plan]
Deliverables: [updates to backlog, decision log, checklist, and a summary of impact]
If you discover scope, architecture, or release-plan impacts, update the relevant docs before finishing.
```

## Example

```text
Work Type: Plan Change
Backlog Item: CW-EPIC-05
Goal: Re-scope purchase flow for MVP
Why: Current implementation path is too large for the September 10, 2026 MVP target
Scope: Update backlog, mark post-MVP items, adjust dependencies, and clarify decision gates
Out of Scope: Code changes unless needed and explicitly requested
Constraints: Follow AGENTS.md, CLAUDE.md, docs/scrum-backlog.md, docs/decision-log.md, docs/release-mvp-checklist.md, and docs/prompt-process.md. Stay within MVP unless explicitly told otherwise.
Definition of Done: docs/scrum-backlog.md and docs/decision-log.md reflect the new plan clearly
Deliverables: Updates to docs/scrum-backlog.md, docs/decision-log.md, and a short summary of delivery impact
```
