shape-revision

What problem does it solve?

Shape the right spec revision when requirements or responsibilities move, so authority and lineage don’t silently drift away from the audit trail.

Core Features & Use Cases

• Revision-first reconciliation: Establishes spec-change intent before delta scoping when policy or doctrine requires revision-first flow.
• Doctrinal path selection: Applies doctrine checkpoints to decide whether to patch an existing spec, create/update a revision, or escalate to consultation.
• Topology-safe authorship: Prevents overlapping or competing truths by closing the current authority branch before creating new artifacts.
• Structured, section-scoped output: Authors revisions with explicit scope, owning context, source/destination specs, requirement movement, and downstream update notes.
• Audit-aware edge handling: Treats evidence as a trigger for explicit reconciliation and supports post-audit correction workflows.

Quick Start

Tell your agent to run shape-revision with the change request, source/destination spec IDs, and the requirement IDs that moved, then have it produce a revision rationale or a direct patch decision using the doctrine pass.