Update to PathToShip

{
  "description": "Keep a launch-readiness record in the repository — which PathToShip checks ran on which commit, what was found, fixed, or accepted, and the operational items no scanner can see. Use after a verify_fix, before a launch or client handoff, or when asked for an audit trail of readiness.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 735
    },
    {
      "relative_path": "assets/icon.png",
      "size_in_bytes": 7687
    }
  ],
  "name": "pathtoship-launch-record",
  "skill_md_contents": "---\nname: pathtoship-launch-record\ndescription: Keep a launch-readiness record in the repository — which PathToShip checks ran on which commit, what was found, fixed, or accepted, and the operational items no scanner can see. Use after a verify_fix, before a launch or client handoff, or when asked for an audit trail of readiness.\n---\n\n# Launch readiness record\n\nA record, not a seal: it states what was checked on which commit and what happened — true on the day it is written and useful to whoever inherits, audits, or pays for the app. The scanner cannot see operations (backups, rollback, on-call), so the record also carries the human's own attestations.\n\n## When\n\n- After a `verify_fix` that resolves findings, or when the verdict reaches `ready`.\n- Before a launch, a public URL, a client handoff, or a compliance/audit conversation.\n- When the user asks \"what did we check?\", \"is there a record?\", or \"what's still open?\".\n\n## Procedure\n\n1. Get the facts from the tools — never from memory: `get_score` (score, verdict, ship bar, weakest dimension, consequence), `get_findings` with `severity_min: \"medium\"` for what remains — **follow `next_offset` until it is null**, since results are paged — and the last `verify_fix` result (resolved / still open / newly introduced). Note the `permalink`. Record the commit only if you know it is the one that was scanned (for example, the user pushed it and the scan ran after); otherwise write `unknown` rather than whatever the branch points to now.\n2. The launch interview is optional — ask whether the user wants to include it. If they do, run it through the tool, not from memory: call `prr_interview` with the `scan_id` to get the thirteen questions and what is already answered. In ChatGPT a form appears — let the user fill it in and save. Elsewhere, ask the unanswered questions briefly and record the answers with `prr_interview` (`answers` keyed by question id: `yes` / `no` / `na` for attestations, a number for rows and bills, short text otherwise; a `note` for context). The tool merges partial answers and returns the recorded state — copy attestations from that result, never from the conversation. Everything it holds is **self-reported** and is never part of the score.\n3. For every remaining finding at medium or above, ask the user which applies and record it: **fix planned** (by when), **accepted risk** (why, by whom), or **not applicable** (why). If they have not decided, write **undecided**. Never invent a deadline, a risk acceptance, or a name, and never silently drop a finding.\n4. Write or update `docs/launch-readiness.md` (create the folder if needed). Keep earlier entries; append the new one at the top. Format:\n\n```markdown\n# Launch readiness — <app name>\n\n## <YYYY-MM-DD> — <milestone, e.g. \"public beta\">\n\n- Commit: `<sha>` on `<branch>` · PathToShip scan `<scan_id>` · <permalink>\n- Score: <before> → <after> (ship bar <ship_bar>) · Verdict: <verdict> · Weakest: <dimension>\n- At 10x users: <consequence line from get_score>\n- Resolved this round: <n> — <titles, one line each>\n- Remaining (medium+): <title> — <fix planned by … | accepted risk: … (name) | n/a: …>\n- Self-reported (from `prr_interview`, <date>): secrets store ✔/✘ · backups restored ✔/✘ · rollback rehearsed ✔/✘ · monitoring + on-call ✔/✘ · staging ✔/✘ · health checks + timeouts ✔/✘ · edge rate limiting ✔/✘ · load test ✔/✘ · tier <…> · largest table <n> rows · last month <$> · autoscale floor <…> · media via <…> (notes: …)\n- Signed off by: <name, role — only if the user gives one; otherwise omit this line>\n```\n\n5. Show the user the entry. Commit it (`docs: launch readiness record <date>`) only if they ask you to; otherwise hand it to them to paste.\n\n## Rules\n\n- Facts come from tool results; attestations come from the user through `prr_interview`; label which is which. `get_score` shows them under `self_reported` — quote that block, do not blend it into the score line.\n- Never write \"resolved\" for anything `verify_fix` did not report as resolved.\n- Do not restate scoring rules or thresholds — quote the tool's numbers.\n- Keep it under a page per entry. It is a record people will actually read.\n- Set `trigger: \"skill\"` on tool calls this skill initiates.\n"
}