---
prompt_version: 1
layer: reconciliation
action: next
---

# Prompt: Reconciliation To Follow-Up Work

Use the reconciliation artifact to identify follow-up planned work.

## 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.
- This prompt is the canonical `next` action for the `reconciliation` layer: it advances only from review evidence into follow-up planning guidance. Do not reuse it as `build`, `review`, or as permission to scaffold a default new artifact family.
- Default this prompt to milestone-level reconciliation evidence produced by implementation handoff. Use task-level reconciliation evidence only when an explicit task-local review exception already exists.
- Extract unresolved review concerns, deferred acceptance criteria, discovered work, and backlog work.
- Recommend whether each item needs a new spec, slice update, phase, milestone, or task.
- Keep follow-up items scoped and traceable.
- Do not silently fold new work into completed work.
- This prompt is read-only by default: it recommends follow-up planning artifacts but does not create them.
- Wording such as `move downstream`, `plan next work`, `identify follow-up work`, or `suggest next step` means report candidate follow-up artifacts and stop unless the user separately invokes the matching `next` prompt or an explicit create/scaffold command.
- If follow-up work spans multiple hierarchy layers, return a proposed scaffold plan with every intended layer named. Nested scaffolding requires an explicit programmatic nested-scaffold request and must not be inferred from reconciliation follow-up language.

## Required Output

Return:

- Follow-up tasks
- Backlog candidates
- Spec or planning updates needed
- Validation or review actions
- Items requiring user decision
