# Plan Template

Every delivery issue must have a persisted plan before code changes. Store it in a stable path such as:

```text
.tmp/devops-plans/<repo>__issue-<number>.md
```

## Plan Template

```text
[issue-plan-v1]
Issue:
- repo:
- number:
- title:
- type:
- trigger source:

Status:
- current: selected
- owner agent:
- reviewer:

Branching:
- target base branch:
- working branch:
- PR:

Problem:

Expected behavior:

Acceptance criteria:
- [ ]
- [ ]

Related scope:
- interfaces/apis:
- directories/files:
- tests:

Allowed path scope:
- path/glob 1
- path/glob 2

Curated context pack:
- issue body/comments
- attachments
- code references
- prior PRs/commits/docs

Implementation notes:

Verification plan:
- build/compile:
- unit/integration:
- e2e:
- smoke path:
- screenshot/browser checks:

Evidence:
- commit:
- pipeline:
- preview url:
- screenshots:

Risk and blockers:

Handoff notes:
```

## Required Status Flow

- `selected`
- `planned`
- `in_progress`
- `pending_test`
- `pending_review`
- `merged`
- `closed`
- `needs_info`
- `blocked`
- `rejected`

## Ownership Rules

- MajorAgent creates and updates the plan before coding starts.
- SubAgent reads only the plan plus minimal code context and updates implementation notes.
- TestAgent updates verification results and may move the status back to `in_progress`.
- Human reviewer confirms `pending_review` to merge readiness.

## Scope Rules

- If the diff touches files outside the allowed path scope, stop and either:
  - update the plan with justification, or
  - request human approval.
- If a new dependency or deprecated technology is introduced, record the compatibility decision in `Risk and blockers`.