{"id":17201,"plugin_id":"plugins_6a746bbb64d48191942c65a16a1eb19f","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:01.412Z","digest":"c5e4ad19e35fccc40837234e65c1e1af9dda4bc0545397f524c324445f21867c","against":null,"payload":{"description":"Turn a rough agent task or project increment into a bounded, independently ratifiable sprint contract with immutable acceptance checks, scope, constraints, autonomy ceiling, budget, escalation, identity, expiry, and receipt fields.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":240}],"name":"goal-contract","skill_md_contents":"---\nname: goal-contract\ndescription: Turn a rough agent task or project increment into a bounded, independently ratifiable sprint contract with immutable acceptance checks, scope, constraints, autonomy ceiling, budget, escalation, identity, expiry, and receipt fields.\n---\n\n# Author a sprint contract\n\nUse `../../assets/sprint-contract.yaml` as the artifact. Read `../../references/philosophy.md` for the two-layer independence rule.\n\nThis skill authors a contract for work that the target system will dispatch.\nIt may contract the current development task only when the user explicitly\nasks for that outcome or an installed ADL/Proctor-style integration requires\nit. Plugin presence alone is not such an integration.\n\n## Workflow\n\n1. Convert the request into one observable outcome. Separate desired effect from implementation method.\n2. Enumerate in-scope and out-of-scope artifacts and mutations.\n3. Write mechanically runnable acceptance checks against ground truth. Put prose review behind an explicit human or distinct-judge gate.\n4. Declare constraints, allowed tools/effects, verifier scope/freshness, autonomy ceiling, attempt/time/token/cost budgets, and ACK escalation.\n5. Identify proposer and ratifier. Leave status `DRAFT`, `ratified_by`, contract hash, and receipt empty until independent ratification actually occurs.\n6. After ratification, hash the immutable contract, issue the receipt, set expiry, and make any acceptance change require revocation and a new contract version.\n\n## Quality rules\n\n- Avoid “works,” “looks good,” or “properly” unless a check defines them.\n- Keep one contract small enough for one fresh-worker move or an explicitly decomposed set of moves.\n- Set the ceiling to propose-only when verifier qualification or mutation coverage is incomplete.\n- Do not fabricate ratification, timestamps, signatures, identities, or receipt references.\n\nReturn the contract plus a plain-language explanation of what can block, quarantine, escalate, or require human judgment.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}