---
prompt_version: 1
layer: milestone
action: recertify
---

# Prompt: Recertify Milestone Overview

Review the selected milestone overview against its parent phase, current repository behavior, workflow direction, and downstream task, implementation, and reconciliation evidence. Decide whether the milestone should remain active as-is, be updated, be collapsed with related milestone scope, be split, be deferred, be marked completed or superseded, or be removed from active planning input.

## Instructions

- Command placeholder: Expand `<day-shift-cli>` to the resolved session invocation. Use `day-shift` for installed/user mode after verification, and use `node dist/cli/index.js` in repository development mode when compiled `dist` output is current.
- Use this prompt when a milestone overview may have become stale because child tasks have progressed, parent phase direction changed, repository behavior diverged, or the milestone has already been satisfied.
- Treat recertification as milestone lifecycle hygiene, not as authorization to create tasks, implementation summaries, or reconciliation artifacts.
- Compare the milestone overview against current repository evidence before deciding disposition:
  - parent phase, slice, and upstream specification evidence
  - child task definitions, implementation summaries, and reconciliation artifacts
  - current workflow, prompt, template, and command guidance
  - implemented CLI commands and tests when the milestone concerns command behavior
- Separate stale wording from stale direction. A milestone can need an update even when its underlying goal remains valid.
- Do not carry forward already-implemented behavior as future scope.
- If related milestone scope now describes one active concern, recommend collapsing it into one milestone and updating parent child declarations.
- If the milestone is fully implemented, replaced, or no longer useful as active planning input, recommend marking it completed, superseded, or archived according to the repository's current lifecycle conventions.
- If the milestone remains valid but should not be planned soon, recommend deferral instead of deleting it.
- Identify required metadata, parent traceability, declared task, and child-artifact cleanup if update, collapse, split, completion, or supersession is recommended.
- Preserve historical traceability where useful, but keep active planning inputs focused on current work.
- Keep the review read-only unless the user explicitly asks you to apply the recertification changes.
- Recertification, second-pass review, hardening, and improvement requests do not authorize downstream planning artifacts. Stop after milestone hygiene recommendations unless the user explicitly asks to create or revise the next planning layer.

## Disposition Options

Use one of these dispositions for each reviewed milestone:

- `keep-active`: the milestone remains current, valid, and useful as active planning input.
- `update-active`: the goal remains valid, but wording, scope, metadata, task declarations, or traceability are stale.
- `collapse`: related active milestone scope should be merged into one current planning input.
- `split`: the milestone now spans distinct concerns that should be separated before further planning.
- `defer`: the milestone remains valid but should not be treated as near-term active planning scope.
- `completed`: downstream evidence satisfies the milestone intent and only closeout or metadata hygiene remains.
- `superseded`: the milestone has been replaced by newer planning direction but should remain available for historical traceability.
- `remove-from-active-planning`: the milestone should no longer be treated as active planning input because it is obsolete, duplicate, or no longer useful.

## Required Output

Return findings grouped as:

- Recertification Scope
- Current Evidence Reviewed
- Disposition By Milestone
- Active Scope To Preserve
- Stale Or Implemented Scope To Remove
- Collapse Or Split Recommendations
- Metadata And Traceability Updates Needed
- Child Artifact Updates Needed
- Workflow Or Prompt Updates Needed
- Dangling Reference Checks
- User Decisions Needed

For each disposition, state:

- the milestone overview path
- the recommended disposition
- why that disposition follows from current evidence
- whether file edits are needed
- whether parent declarations or child planning references must change
