to-tickets
Break the spec into small, independently-implementable tracer-bullet vertical slices. No checkpoint gate — hands off directly to wayfinder for implementation orchestration.
- License 许可
- MIT
- 最近更新
- 2026-08-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- to-tickets
- description
- Break the spec into small, independently-implementable tracer-bullet vertical slices. No checkpoint gate — hands off directly to wayfinder for implementation orchestration.
03 SKILL.md 正文
To-tickets
Tracer-bullet vertical slices, not horizontal layers. Each ticket should be independently implementable and deliver end-to-end behavior, even if narrowly. Never "build the database layer" → "build the API" → "build the UI" as three tickets that are each individually useless.
The principle: make the change easy, then make the easy change. If a ticket requires prefactoring, that prefactoring is its own ticket listed as a blocker.
Process
-
Read the spec (or
CONTEXT.mdsummary for script-tier) and.agent/state.jsonfor the doc tier and issue tracker. -
Gather context. Fetch referenced materials, explore the codebase to understand where changes land.
-
Break the work into tracer-bullet slices. Each slice:
- Sized to one context window — small enough to implement and
review inside a single fresh context, before the window fills and
attention degrades (see the "Smart zone" note in
reference/context-budget.md). One ticket ≈ one context window is the sizing rule, not a rough guideline. If a slice can't plausibly be finished and reviewed before a context reset, it's too big — split it. - Complete enough to demo or verify on its own.
- Ordered with explicit blocking dependencies.
- Sized to one context window — small enough to implement and
review inside a single fresh context, before the window fills and
attention degrades (see the "Smart zone" note in
-
Special case — wide refactors. Use expand-contract:
- Expand: add the new form alongside the old.
- Migrate: batch changes by blast radius (smallest first).
- Contract: remove the old form once no references remain.
-
Match granularity to tier:
- Script / tool: flat list, dependencies rarely matter.
- App / system: explicit dependency tracking (B depends on A).
-
Write tickets to the configured tracker (
issue_trackerin state.json): local files indocs/agents/tickets/, or via GitHub/ Linear. Each ticket includes:- Title
- Description of end-to-end behavior delivered
- Acceptance criteria
- Blocking dependencies (if any)
Each ticket is self-contained — restate context rather than assuming the reader has the spec open.
-
Present the breakdown to the user — what each slice does, in what order, and why. If risk_posture is
"careful", explicitly note that implementation will pause after each ticket for confirmation. -
Hand off to wayfinder's implementation orchestration — it will invoke
skills/implement/SKILL.mdper ticket, respecting risk posture.
What this skill must never do
- Never produce horizontal-layer tickets where intermediate tickets don't independently do anything verifiable.
- Never silently reorder or drop a slice without flagging it.
- Never start implementation itself — hand off to wayfinder.
04 同仓库更多 Skills
wayfinder
The orchestration hub for all work. Creates a map of investigation tickets (grilling, research, prototype, task, bug), resolves them one at a time with strict grilling discipline, manages risk posture pauses during implementation, and hands off to to-spec when the map is complete. Use for any work regardless of size — a trivial task has a small map, a large migration has many tickets.
to-spec
Synthesize a specification from the completed wayfinder map. Never runs its own interview — it only writes down what wayfinder's grilling tickets already established, at a depth proportional to the project's documentation tier.
tdd
Reference material for test-driven development discipline. Red before green, one slice at a time. Use as reference during implementation, not as a step-by-step procedure.
start-session
Orient a new session in any project directory. Detects empty directory, existing codebase, or resume state, gathers cheap signals, and routes to wayfinder. The only user-invoked entry point.
setup
Configures the issue tracker. Called by start-session during first orient. Model-invoked — runs automatically as part of the flow, not user-triggered.
scope-lock
Produces a short context manifest of which files and directories are in-bounds for the current task on a medium or large existing codebase. Keeps subsequent reading inside that boundary unless explicitly widened. Prevents context bloat.