Issue Contract Writer

Draft and validate an implementation issue before its parent/controller publishes or materially amends it. This skill produces contract text and evidence; it never creates, edits, labels, assigns, links, or closes a GitHub issue.

Establish the source record

Read and record the sources that can govern the proposed work:

1. Resolve the repository root and every applicable AGENTS.md in its filesystem and repository hierarchy.
2. Read the product, engineering, architecture, policy, validation, and operational documents named by that guidance. Resolve relative links from the document that names them.
3. Inspect current implementation and tests for the behavior the issue would change. Record the exact revision or working-tree state inspected.
4. Read related issues, pull requests, comments, native parent/sub-issue links, blocked-by and blocking relationships, and other dependencies that can change scope or sequencing.
5. Record source authority, exact revision or immutable identity, relevant evidence, and the reconciliation performed before drafting each material requirement.

If a required source, dependency, relationship, or exact target cannot be inspected, return Conclusion: Evidence blocked with the missing evidence and action needed. If sources materially conflict and no authority resolves the conflict, stop for an owner decision; do not choose a requirement silently.

Draft a finite delivery contract

The issue must contain these sections, even when a section says None: