What problem does it solve? Project-specific agent instruction files (AGENTS.md) drift out of sync with requirements and design documents, get edited by hand without provenance, or are created when they are not needed. This Skill maintains the smallest durable, evidence-backed project instruction contract for one exact selected project, with deterministic rendering, explicit ownership tracking, and guarded recovery. ## Core Features & Use Cases - Receipt-bound decisions: Replays a maintainer-issued spec-validation receipt before trusting requirements or design, then decides between created, attached, refreshed, adopted, retired, existing-sufficient, or not-needed outcomes. - Deterministic rendering: Renders rules into six fixed sections with hard limits (12 rules, 256 bytes per rule, 4 KiB body) without mutating the repository until an authorized apply step. - Ownership and recovery: Tracks managed regions through a workspace-private registry, preserves human-authored prefixes byte-for-byte, and fails closed on lock files, backups, legacy markers, or conflicting evidence. - Use Case: After validating docs/requirements.md and docs/design.md, route an explicit project-instruction decision here to attach a managed compatibility-rules tail to an existing AGENTS.md while preserving every human-written byte. ## Quick Start Ask the agent to use project-agent-instructions to inspect the selected project with its current spec receipt and decide whether an AGENTS.md update is needed.
