slice-issues
Slice GitHub parent issues into reviewable real sub-issues. Use when Codex is asked to split, slice, decompose, refine, or plan a GitHub issue into child issues, sub-issues, implementation slices, or reviewable follow-up issues before implementation work begins.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 4
- Forks
- 2
01 前言 Front Matter
- name
- slice-issues
- description
- Slice GitHub parent issues into reviewable real sub-issues. Use when Codex is asked to split, slice, decompose, refine, or plan a GitHub issue into child issues, sub-issues, implementation slices, or reviewable follow-up issues before implementation work begins.
03 SKILL.md 正文
Slice Issues
Overview
Use this workflow to decompose a GitHub issue into reviewable implementation slices before code changes begin. Prefer real GitHub sub-issues over textual task lists so the backlog remains traceable and each slice can have its own acceptance criteria, branch, PR, and verification.
This skill is GitHub-specific but engine-independent. Keep runtime-specific
integration details in adapters/.
Required Reading
../references/issue-labels.mdbefore creating child issues, to set each slice's issue type and labels so the backlog and any project board can filter them.
Workflow
-
Identify the parent issue number or URL.
-
Read the parent issue body and comments before slicing.
-
Check existing open issues to avoid duplicate slices.
-
Decide whether the work should be split into sub-issues or kept in one PR with clearly separated commits.
-
For each sliced task, create a child issue with GitHub's sub-issue support, setting its type and labels per
../references/issue-labels.md. Use exactly one type representation — a native issue type or atype:label, never both:# Org repos with native issue types: gh issue create --parent <parent> --title "<title>" --body-file <file> \ --type <Type> --label "<area>,<grouping>" # Personal repos (native issue types unavailable) — carry the type as a label: gh issue create --parent <parent> --title "<title>" --body-file <file> \ --label "<type-label>,<area>,<grouping>"A slice is normally a
user-story(a reviewable slice of value) or atask(technical work with no direct user value). Use--body-fileinstead of--bodywhen the body is multi-line or contains Markdown that would be awkward to quote safely. -
Comment on the parent issue with the created child issue links and the recommended implementation order.
-
Report the created child issues and any fallback used.
Slicing Rules
- Make each child issue independently reviewable and small enough for one focused PR.
- Give each child issue a clear goal, scope, and acceptance criteria.
- Give each child issue an explicit type and labels per
../references/issue-labels.md— exactly one type representation (a native issue type or atype:label) plusarea:and any project grouping such as a roadmap phase — so it can be triaged onto a project board without re-reading the body. Do not encode workflow status in labels; that belongs to the board. - Preserve the parent issue as the coordination point.
- Prefer dependency order over arbitrary numbering.
- Keep implementation work out of the slicing step unless the user explicitly asks to continue into implementation.
- If a slice is only documentation, validation, generator behavior, or example refresh work, make that boundary explicit in the title and acceptance criteria.
Fallback
Use body links or Markdown task lists only when GitHub sub-issue creation is unavailable or rejected by the CLI/API.
When fallback is used:
- Include the exact command that failed.
- Include the exact error returned by the CLI/API.
- Add the fallback links or task list to the parent issue.
- State in the final report that real sub-issues could not be created.
Relationship To Issue Implementation
After slicing is complete, use ../implement-issue-workflow/SKILL.md for each
child issue that needs implementation, branch, commit, push, and pull request
work.
04 同仓库更多 Skills
traceability-review
Review explicit architecture traceability metadata for gaps, inconsistencies, unsupported claims, stale links, dangling references, and metamodel violations. Use when Codex needs to inspect artifact relations, validate ADR-to-risk or quality-scenario coverage, propose relation updates, or produce an evidence-backed traceability review report.
risk
Create proposed architecture risk artifacts and analyze their traceability to ADRs, quality scenarios, requirements, components, controls, and evidence. Use when Codex needs to identify, draft, update, prioritize, or review architecture risks, separate risks from issues and decisions, propose mitigations, or produce a risk impact report without deciding acceptance.
quality-scenario
Create proposed quality scenarios and analyze their traceability to quality objectives, ADRs, risks, requirements, architecture artifacts, and code evidence. Use when Codex needs to draft or update measurable quality scenarios, inspect existing arc42 Chapter 10 quality requirements, derive scenarios from source evidence without inventing targets, propose metadata relations, or produce a quality scenario impact report.
presentation
Create or update docs-as-code presentation material as AsciiDoc reveal.js decks rendered with docs-toolbox. Use when Codex needs to prepare talks, meetup or conference proposals, speaker notes, demo scripts, event-specific artifacts under talks/, or slide decks that must remain repository-native rather than PowerPoint or Google Slides files.
pr-review
Review GitHub pull requests and proposed branch changes for correctness, regressions, missing tests, documentation-contract violations, traceability gaps, and reviewability. Use when an AI assistant is asked to review a PR, review pull request changes, inspect a PR branch before merge, or produce PR review comments.
post-merge-sync
Synchronize a local checkout after a pull request has been integrated: verify a clean worktree, switch to the base branch, fast-forward from the remote, confirm the PR changes are present, and clean up local and remote PR branches when safe. Use when an agent is asked to clean up after an integrated PR or return the repository to the latest base branch.