to-issues — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited to-issues (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Source: mattpocock/skills - engineering/to-tickets
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
Target the project's issue tracker directly - GitHub via gh or Jira via acli, per rules/git-conventions.md and the jira skill. Use whatever label the tracker already uses to mark agent-ready work.
Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
Look for opportunities to prefactor the code to make the implementation easier - "make the change easy, then make the easy change." Any prefactoring should be its own issue, sequenced first. (review-time: see section note)
why-no-hook: skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state).
Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
<vertical-slice-rules>
(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)</vertical-slice-rules>
Give each issue its blocking edges - the other issues that must complete before it can start. An issue with no blockers can start immediately. (review-time: see section note)
Wide refactors are the exception to vertical slicing. A wide refactor is one mechanical change - rename a column, retype a shared symbol - whose blast radius fans across the whole codebase, so a single edit breaks many call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as expand-migrate-contract. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites in batches sized by blast radius (per package, per directory), each batch its own issue blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in an issue blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify issue - green is promised only there. (review-time: see section note)
Present the proposed breakdown as a numbered list. For each slice, show:
(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)Ask the user:
(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)Iterate until the user approves the breakdown.
For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.
Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
Work the frontier: any issue whose blockers are all done - for a purely linear chain that means top to bottom. Implementation happens one issue at a time via /build, clearing context between issues. (review-time: see section note)
<issue-template>
A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
Avoid specific file paths or code snippets - they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts - not a working demo, just the important bits.
(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)Or "None - can start immediately" if no blockers.
</issue-template>
Do NOT close or modify any parent issue.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.