mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-14 21:16:36 +03:00
Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
c568bac43e
Issue/ticket bodies emitted from a delivery run must be written for a cold
reader: a contributor with none of the session context and no access to the
agent's local artifacts. Encode this at the change-contract layer so any run
that emits tracker artifacts inherits it.
- templates/change-contract.md: new "Issue/ticket body (cold-reader
requirement)" section listing the five requirements (background naming the
investigation, complete inline evidence with file:line refs, reproduction
commands runnable by a stranger, acceptance-criteria checkboxes, no
agent-local paths or private-artifact references), plus a header-note
pointer with the litmus test.
- references/journey.md: journey-level statement of the requirement plus
pointers at phase 1 (intake output row) and phase 5 (verification-planning
output row) where tracker artifacts are emitted.
- evals/evals.json: add case cold-reader-issue-body-gate covering a body draft
that references off-repo artifacts ("artifact pyramid", local /tmp ledger,
detail available on request) and must be rejected/rewritten by the gate.
Closes #385
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
4.3 KiB
4.3 KiB
Change Contract
Fill this in at Framing (Stage 1). Keep it short. A contract that needs a page is hiding an ambiguity — surface it instead. One standing exception: any issue or ticket body this run emits must be self-contained for a cold reader (see the Issue/ticket body section). Litmus test: could someone who found the body via search act on it without asking anyone anything?
Change-request provenance
- Change-request URL or number:
- Source type:
- Repository:
- Base ref:
Problem
Authority
Constraints
Affected system boundary
Risks
Non-goals
Acceptance criteria
Declared verification target
Decision: change warranted?
Skip reason
Issue/ticket body (cold-reader requirement)
- Background section: names the investigation — tools used with links, date, scope, and a sketch of the method.
- Complete inline evidence: the full affected list with
file:linereferences in the target repository. No samples-plus-"on request": anything promised for later must instead be included now. - Reproduction commands: runnable by a stranger on a fresh checkout.
- Acceptance criteria as checkable checkboxes.
- No agent-local paths or private-artifact references in the public body (scratch directories, local evidence ledgers, delivery packets). If evidence lives only outside the repository, inline it.
Gate verdict
- Gate identifier:
- Verdict:
- Evidence:
- Head SHA:
PR / CI status
- PR number:
- CI status: