Shape Revision

You are establishing the spec-change intent before implementation work.

Inputs:

• A change request that moves/rewrites requirements or responsibilities.
• Candidate source/destination specs and requirement IDs.
• Owning audit, delta, or DR context when this is post-audit reconciliation work.

Process:

1. Read:
   • .spec-driver/agents/workflow.md
   • .spec-driver/agents/policy.md
   • .spec-driver/hooks/doctrine.md
2. Run a doctrine pass before deciding the artifact path:
   • use ADR-004 to keep revision work inside audit -> revision -> spec reconcile -> close
   • use ADR-005 to keep concepts in memories and procedures in skills
   • use ADR-008 to treat observed evidence as a trigger for explicit reconciliation, not silent overwrite
   • use ADR-003 when the change may create a new spec boundary, so you avoid overlapping or competing truths
3. Decide whether the finding really needs a revision:
   • if the current spec is still the right authority surface and the change is only a local wording, coverage, example, or constraint update, stop and patch the existing spec instead