---
prompt_version: 1
layer: reconciliation
action: build
---

# Prompt: Build Task-Level Reconciliation Exception

Use the task definition, implementation summary, and repository context to create or update task-level reconciliation when one task needs its own review boundary.

## 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.
- Prefer command-supported reconciliation build/review/update, validation, and metadata sync surfaces before inference or manual artifact edits. Review and validation output remains read-only evidence unless a separate write command is explicitly selected.
- When task-level reconciliation records command-surface follow-up, use `<day-shift-cli> commands inventory --format json` as read-only evidence for command availability, write posture, selected-artifact requirements, callable versus registry-only state, and mixed-posture families before classifying residual or follow-up work.
- Create missing canonical artifacts only for the selected layer. When revising an existing artifact, update it in place and do not create sibling, child, paired, or alternate artifacts unless the current user request explicitly asks for that creation step.
- Compare intended work with completed work.
- Preserve existing user-authored content when updating an existing reconciliation artifact.
- When revising an existing reconciliation artifact, refresh reconciliation status, upstream traceability, and other front matter metadata so it reflects the current review state rather than the original draft state. Use `<day-shift-cli> reconciliation update` for CLI-supported reconciliation metadata transitions when available; direct front matter edits require an explicit manual exception.
- Review acceptance criteria and validation evidence.
- Separate planned work, discovered work, backlog work, accepted residual work, and follow-up tasks.
- Use `Accepted Residual Work` only for reviewed gaps or deferred adoption that do not block acceptance; state why each item is non-blocking.
- Record follow-up tasks and review concerns.
- Use `reconciliation_status`: `pending`, `reviewed`, `accepted`, `rejected`, or `deferred`.
- Do not mark work accepted unless review evidence supports it.
- If a direct metadata edit appears necessary where a CLI update or sync command exists, stop before editing and report the command considered, why it cannot be used, the manual exception, and the artifact fields that would change.
- Prefer milestone-level reconciliation by default; use this prompt only when task-level review is materially justified.
- Stop and report instead of guessing when the selected artifact and review evidence conflict materially.
- Use repository-relative paths throughout the artifact.
- Preserve the canonical artifact-shape contract from `.day-shift/specs/06-templates-and-prompts/templates.md`: one visible H1, the required H2 section names in order, parser-safe none-state formatting where applicable, and no leaked scaffolding prose or unresolved placeholders in the saved artifact.

## Template Reference

Use `.day-shift/templates/reconciliation.md` as the artifact shape.

## Required Output

Create or update a reconciliation artifact with the configured template sections and valid front matter.
