development-contract-systemlisted

# Development Contract System Use this skill when a repository needs a deterministic, reviewable workflow for tracking substantive work through repo-owned feature records instead of ad hoc notes. This skill is self-contained on purpose so it can be moved into another repo or skill collection without depending on the smaller contract skills from this frame at runtime. When the target repo uses local skills, generate a thin overlay with its concrete policy and helper commands. Reference `development-contract-process` only when the target agent has that skill; otherwise include the minimum operator flow. Build or port the system only within the requested scope. Review and design requests return findings or a draft without creating policy, records, helpers, or new enforcement. Preserve an existing system until its migration is explicit. ## What this skill builds A complete repository-local contract system with these parts: - a repo-owned policy file - a `feature_records/` directory with lifecycle subdirectories - a Markdown template for new records - a root `feature_records/README.md` - a checker script that validates record structure and changed-path coverage - a lifecycle transition helper script - direct shell tests for the checker and lifecycle helper - repo docs that explain how maintainers should use the system - optionally, a repo-local process overlay skill that points at the concrete policy file, checker command, helper command, and validation profiles Recommend