---
prompt_version: 1
layer: task
action: recertify
---

# Prompt: Recertify Task Definition

Review the selected task definition against its parent milestone, current repository behavior, workflow direction, implementation evidence, and any task-level reconciliation exception artifact. Decide whether the task should remain ready or active as-is, be updated, be split, be collapsed with related task scope, be deferred, be marked completed or superseded, or be removed from active implementation 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 task definition may have become stale because implementation has progressed, sibling task evidence changed the plan, repository behavior diverged, or the task has already been satisfied.
- Treat recertification as task lifecycle hygiene, not as authorization to implement the task or write implementation summaries.
- Compare the task definition against current repository evidence before deciding disposition:
  - parent milestone, phase, slice, and upstream specification evidence
  - paired `implementation-summary.md` and task-level `reconciliation.md` when present
  - sibling task definitions and completed summaries when they affect readiness or duplicate scope
  - current workflow, prompt, template, and command guidance
  - implemented code, tests, and command behavior for target paths named by the task
- Separate stale wording from stale direction. A task can need an update even when its underlying goal remains valid.
- Do not carry forward already-implemented behavior as future scope.
- If related task scope now describes one active concern, recommend collapsing it into one task and updating parent child declarations.
- If the task is fully implemented, replaced, or no longer useful as active implementation input, recommend marking it completed, superseded, or archived according to the repository's current lifecycle conventions.
- If the task remains valid but should not be implemented soon, recommend deferral instead of deleting it.
- Identify required metadata, readiness, parent traceability, target-path, dependency, paired-summary, and reconciliation cleanup if update, collapse, split, completion, or supersession is recommended.
- Preserve historical traceability where useful, but keep active implementation 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 implementation or downstream reconciliation. Stop after task hygiene recommendations unless the user explicitly asks to implement, update metadata, or reconcile.

## Disposition Options

Use one of these dispositions for each reviewed task:

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

## Required Output

Return findings grouped as:

- Recertification Scope
- Current Evidence Reviewed
- Disposition By Task
- Active Scope To Preserve
- Stale Or Implemented Scope To Remove
- Collapse Or Split Recommendations
- Metadata, Readiness, And Traceability Updates Needed
- Paired Summary Or Reconciliation Updates Needed
- Workflow Or Prompt Updates Needed
- Dangling Reference Checks
- User Decisions Needed

For each disposition, state:

- the task definition path
- the recommended disposition
- why that disposition follows from current evidence
- whether file edits are needed
- whether parent declarations, target paths, dependencies, or paired evidence must change
