---
prompt_version: 1
layer: slice
action: recertify
---

# Prompt: Recertify Slice Overview

Review the selected slice overview against the upstream specification, current repository behavior, workflow direction, and downstream phase, milestone, task, implementation, and reconciliation evidence. Decide whether the slice should remain active as-is, be updated, be collapsed with related slice 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 slice overview may have become stale because implementation has progressed, upstream spec direction changed, child planning artifacts diverged, or the slice has already been satisfied.
- Treat recertification as slice lifecycle hygiene, not as authorization to create phases, milestones, tasks, implementation summaries, or reconciliation artifacts.
- Compare the slice overview against current repository evidence before deciding disposition:
  - upstream specification and spec-index entries
  - child phases, milestones, tasks, implementation summaries, and reconciliation artifacts
  - current workflow, prompt, template, and command guidance
  - implemented CLI commands and tests when the slice concerns command behavior
- Separate stale wording from stale direction. A slice can need an update even when its underlying goal remains valid.
- Do not carry forward already-implemented behavior as future scope.
- If related slice scope now describes one active concern, recommend collapsing it into one active slice overview and updating traceability.
- If the slice 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 slice remains valid but should not be planned soon, recommend deferral instead of deleting it.
- Identify required metadata, upstream traceability, linked-spec, 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 slice 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 slice:

- `keep-active`: the slice remains current, valid, and useful as active planning input.
- `update-active`: the goal remains valid, but wording, scope, metadata, child declarations, or traceability are stale.
- `collapse`: related active slice scope should be merged into one current planning input.
- `split`: the slice now spans distinct concerns that should be separated before further planning.
- `defer`: the slice remains valid but should not be treated as near-term active planning scope.
- `completed`: downstream evidence satisfies the slice intent and only closeout or metadata hygiene remains.
- `superseded`: the slice has been replaced by newer planning direction but should remain available for historical traceability.
- `remove-from-active-planning`: the slice 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 Slice
- 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 slice overview path
- the recommended disposition
- why that disposition follows from current evidence
- whether file edits are needed
- whether child planning or traceability references must change
