القائمة
Split settled conversation or an implementation-ready artifact into independently deliverable tracer-bullet tickets when explicit work decomposition is useful.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill to rebase gh-stack branches and resolve conflicts. Replaces raw git rebase for stack workflows. Triggers: restack, rebase, rebase on main, branches out of date, resolve conflicts.
Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.
Use this skill to push a gh-stack stack and create or update stacked pull requests. Replaces git push and gh pr create for stack workflows. Triggers: push, ship it, send this up, submit, update PRs, create PR, push stack, send PRs.
Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.
Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.
Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.
| name | to-tickets |
| description | Split settled conversation or an implementation-ready artifact into independently deliverable tracer-bullet tickets when explicit work decomposition is useful. |
| disable-model-invocation | true |
Turn settled work into tracer-bullet tickets when the user explicitly wants separately tracked work units.
Load /vault before reading or publishing artifacts.
Use settled conversation as the source when no artifact is supplied. When the user supplies a vault artifact, resolve it with vlt read <stem> --depth 2. Require clear scope, implementation approach, acceptance criteria, and verification regardless of source shape. Report missing information and stop when the work is not implementation-ready.
Inspect enough current code and tests to verify the proposed slices against real integration points, dependencies, and test seams. Preserve the source scope and decisions.
Each ticket:
Use expand-migrate-contract only when a wide change cannot stay green as independent vertical slices.
Map every source acceptance criterion or settled requirement to one or more tickets. Merge slices that only produce scaffolding, and split slices that exceed one coherent implementation session. Resolve material ambiguity with the user before publishing.
Create blockers first:
vlt create --type ticket --topic "<ticket title>" --tags "stage/ready-for-agent" --json
vlt update <ticket-stem> --stdin --json
When a source artifact exists, record and link it:
vlt link <ticket> <source> --type derives-from --annotation "Implements one vertical slice"
vlt link <ticket> <blocker> --type blocked-by --annotation "Requires <capability> first"
Use this body:
## Status
ready_for_agent
## What to Build
The end-to-end behavior this ticket delivers.
## Source Coverage
- Source acceptance criterion or settled requirement covered by this ticket.
## Acceptance Criteria
- [ ] Independently verifiable ticket result.
## Verification
- Check or test that proves completion.
## Blocked By
- Linked ticket title, or `None - can start immediately`.
## Out of Scope
- Adjacent behavior owned elsewhere.
## Delivery Evidence
Pending implementation.
Report every ticket, covered spec criteria, blocking edges, and the initial frontier. A frontier ticket has ready_for_agent status and no incomplete blocker.