deliverable-consistency

name	deliverable-consistency
description	Run a deliverable-local consistency sweep across production documents in one deliverable. Use when checking for unresolved markers, missing core artifacts, identity-label mismatches, or candidate unsourced numeric statements.
compatibility	Chirality TASK with DELIVERABLE_TASK profile; local repo tools only.
allowed-tools	python3 tools/validation/scan_deliverable_consistency.py:*
metadata	{"chirality-skill-version":"1","chirality-task-profile":"DELIVERABLE_TASK"}

SKILL — deliverable-consistency

Purpose

Run a deliverable-local consistency sweep across the production documents in one deliverable.

This skill is meant to work with:

• TaskProfile: DELIVERABLE_TASK

It helps the agent:

• surface contradictions,
• find unresolved TBD / ASSUMPTION / CONFLICT: markers,
• identify unsourced numeric parameters,
• spot identity mismatches across the document set,
• and propose minimal corrective edits when authorized.

Suitable agent shells

• TASK with TaskProfile: DELIVERABLE_TASK

Inputs

Required

• DeliverablePath via DELIVERABLE_TASK

Optional

• Tasks
• RuntimeOverrides.FocusDocs
• RuntimeOverrides.Strictness
• RuntimeOverrides.MaxFindings
• RuntimeOverrides.CheckIdentity
• RuntimeOverrides.CheckUnsourcedNumerics

Runtime overrides

Key	Meaning	Default
FocusDocs	Limit the sweep to named production docs	all production docs
Strictness	conservative or aggressive finding posture	conservative
MaxFindings	Soft cap on reported findings	10
CheckIdentity	Check folder/document naming consistency	true
CheckUnsourcedNumerics	Flag numeric statements needing evidence review	true

Tool usage

Preferred deterministic helper:

• tools/validation/scan_deliverable_consistency.py

Preferred method:

• run the deterministic scan first
• read only the flagged deliverable-local files and nearby context
• compare files directly where the deterministic scan cannot decide
• recommendation-first output through DELIVERABLE_TASK

Disallowed behavior:

• no widening scope beyond the single deliverable
• no edits outside the files already permitted by DELIVERABLE_TASK
• no silent conflict resolution

Outputs

• PROPOSAL: blocks for consistency issues
• MISSING: items where files or references are absent
• NEEDS_HUMAN_RULING: items for true contradictions
• optional applied minimal edits if ApplyEdits: true
• updated MEMORY.md through DELIVERABLE_TASK closeout

Non-negotiable constraints

• Every finding must cite a file and best-effort section/heading.
• Unknowns remain TBD.
• Conflicts must be surfaced, not reconciled silently.
• Proposed edits should be minimal and reversible.

QA expectations

• Findings are scoped to one deliverable.
• The deterministic scan should be run first unless the brief explicitly forbids tool use.
• Findings are grouped by issue type where practical.
• Identity mismatches and unresolved markers are explicitly reported when found.
• If no meaningful issues are found, the run should say so explicitly rather than padding output.