SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsto-issues

to-issues

General & other

View repository

Updated 10-16 01:38

About this skill

To Issues

Break a plan into independently-grabbable issues using vertical slices (tracer bullets).

Break a plan into independently-grabbable issues using vertical slices (tracer bullets).

The issue tracker and triage label vocabulary should already be provided to you—if not, run /setup-matt-pocock-skills。

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Process

1. Gather context

Work from what 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.

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.

2. Explore the codebase (optional)

If you have not already explored the codebase, explore it to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary terms and respect the ADRs for the areas you are modifying.

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.

3. Draft vertical slices

Break the plan intotracer bullet issues. Each issue is a thin vertical slice that cuts through all integration layers, not a horizontal slice of one layer.

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 can be "HITL" or "AFK". HITL slices require human interaction, such as architectural decisions or design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL whenever possible.

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.

4. Quiz the user

Present the proposed breakdown as a numbered list. For each slice, show:

Present the proposed breakdown as a numbered list. For each slice, show:

  • Title: a short descriptive name

    Short descriptive name

  • Type：HITL / AFK
  • Blocked by: which other slices (if any) must be completed first

    Which other slices (if any) must complete first

  • User stories covered: which user stories this addresses (if the source material has them)

    Which user stories this addresses (if the source material has them)

Ask the user:

Ask the user:

  • Does the granularity feel right? (too coarse/too fine)

    Does the granularity feel right? (too coarse / too fine)

  • Are the dependencies correct?

    Are the dependency relationships correct?

  • Should any slices be merged or split further?

    Should any slices be merged or split further?

  • Are the right slices marked as HITL and AFK?

    Are the correct slices marked as HITL and AFK?

Iterate until the user approves the breakdown.

Iterate until the user approves the breakdown.

5. Publish the issues to the issue tracker

For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for an AFK agent, so publish them with the correct triage label unless otherwise instructed.

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 (publish blockers first) so that you can reference real issue identifiers in the "Blocked by" field.

Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.

A reference to the parent issue on the issue tracker (if the source is an existing issue, otherwise omit this section).

A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not the layer-by-layer implementation.

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 quickly. Exception: if the prototype produced a snippet that encodes a decision more precisely than prose (state machine, reducer, schema, type shape), inline it here and briefly note it came from the prototype. Trim to the decision-rich parts—not a runnable demo, just the important parts.

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.

Acceptance criteria

  • Criterion 1
  • Criterion 2
  • Criterion 3

Blocked by

  • Reference to the blocking ticket (if any)

    A reference to the blocking ticket (if any)

Or "None—can start immediately" if there are no blockers.

Or "None - can start immediately" if no blockers.

Do not close or modify any parent issue.

Do NOT close or modify any parent issue.