Issue slice drafter

Skill zaixincheng174-ai/codex-agent-governance-skills/core/skills/issue-slice-drafter

Codex governance skill pack for AI coding agents: lifecycle gates, repo preflight, diff-scope audit, evidence closeout, and capability-delivery checks.

Install

npx -y skills add zaixincheng174-ai/codex-agent-governance-skills --skill issue-slice-drafter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Draft implementation-ready vertical tracer-bullet slices from a plan, PRD, audit finding, or Goal Contract. Adapted from to-issues; produces draft issue bodies only and never publishes or labels issues without explicit approval.

SKILL.md

3.2 KB, as published. Nobody here has run it

issue-slice-drafter

Source repo: https://github.com/mattpocock/skills Source path: skills/engineering/to-issues/SKILL.md Source commit: b8be62ffacb0118fa3eaa29a0923c87c8c11985c Local adaptation note: Adapted from an issue-publishing workflow into a read-only drafting skill. It keeps vertical tracer-bullet slicing, HITL/AFK classification, dependencies, and acceptance criteria, while removing automatic issue tracker writes.

Purpose

Turn an approved plan or clarified goal into draft slices that are independently understandable and verifiable.

Each slice should be a thin vertical tracer bullet through the relevant layers, not a horizontal task such as "build backend" or "write UI".

Activation

Use when the user asks to break down work into issues, slices, implementation tickets, agent-ready tasks, or a next-action board.

This skill may also be used after a Goal Contract or audit finds a clear implementation backlog, but only as a drafting step.

Slice Requirements

For each draft slice include:

Title:
Type: HITL or AFK
Parent/source:
What to build:
Acceptance criteria:
Dependencies:
Verification:
Out of scope:
Evidence references:

Classification:

HITL: requires human decision, product judgment, design review, credential access, approval, or high-risk interpretation.
AFK: can be implemented and verified from available repo context and explicit acceptance criteria.

Workflow

Gather source material from the current conversation, Goal Contract, plan, PRD, audit finding, or referenced file.
If repo evidence is needed to avoid vague slices, inspect the relevant code/docs first.
Draft the smallest useful set of vertical slices.
Mark dependencies explicitly.
Include acceptance criteria and verification commands or evidence expectations where known.
Ask for approval before any issue tracker action.

Forbidden actions

Do not publish GitHub issues, GitLab issues, Linear tickets, labels, comments, PRs, branches, commits, or pushes without explicit approval.
Do not run gh issue create or equivalent issue tracker commands unless the user explicitly approves that exact action.
Do not apply labels or mark anything ready-for-agent unless the user explicitly approves.
Do not modify parent issues or source documents.
Do not edit AGENTS, update CONTEXT.md, create ADR, deploy, git push, or run setup.
Do not turn a narrow Goal Contract into a broad backlog.

Stop conditions

Stop when:

The source goal is not clear enough to slice safely.
The requested output would require publishing rather than drafting and approval is absent.
A slice cannot be made independently verifiable.
The work is single-step and an issue breakdown would add noise.

Output Pattern

Issue Slice Drafts
Source:
Assumptions:
Slices:
1. <title>
   Type:
   Dependencies:
   Acceptance criteria:
   Verification:
Publishing status: draft only; no issue tracker writes performed