to-issues

Convert plans into linked issues with acceptance criteria and blockers.

228|68|Updated Sep 27, 2023
One-click install
npx skills add https://github.com/SwitchbackTech/compass-calendar --skill to-issues-switchbacktech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/SwitchbackTech/compass-calendar/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/SwitchbackTech/compass-calendar --skill to-issues-switchbacktech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Core Features & Use Cases

  • Break plans, specs and PRDs into a linked set of end-to-end issues that map to the project glossary.
  • Create implementation tickets and triage-ready work items aligned with acceptance criteria and ADRs.
  • Use tracer-bullet vertical slices to ensure each issue delivers a complete path across schema, API, UI, and tests.

Quick Start

Provide a project plan or PRD and I will convert it into tracer-bullet issues that can be tracked end-to-end.

Frequently Asked Questions about to-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a PRD into independently grabbable issues using vertical slices?

Breaking a PRD into grabbable issues uses tracer-bullet vertical slices to split plans into end-to-end tickets across schema, API, UI, and tests. This ensures each issue delivers a complete functional path with acceptance criteria and blockers.

What is a tracer-bullet vertical slice in issue tracking?

A tracer-bullet vertical slice in issue tracking is a thin, end-to-end implementation path spanning schema, API, UI, and tests. It converts a plan into linked issues that deliver complete functionality rather than horizontal architectural layers.

Can I convert a software spec into linked issues with acceptance criteria automatically?

Yes, converting a software spec into linked issues generates a set of tracked tickets mapped to the project glossary. Each issue includes acceptance criteria, blockers, and end-to-end vertical slice coverage across schema, API, UI, and tests.

Do I need a repository context to break a plan into tracer-bullet issues?

Yes, breaking a plan into tracer-bullet issues requires a repository context or issue reference. This provides the necessary project glossary and structural mapping to generate accurately linked issues with defined acceptance criteria and blockers.

Does breaking plans into vertical slices work for user stories and specs?

Breaking plans into vertical slices applies to plans, specs, PRDs, and user stories for software projects. The process outputs a set of linked issues detailing end-to-end vertical slices across schema, API, UI, and tests with acceptance criteria.

What's the best way to create triage-ready work items from a project plan?

Creating triage-ready work items from a plan involves splitting it into tracer-bullet vertical slices. This produces linked implementation tickets aligned with acceptance criteria and ADRs, detailing complete paths across schema, API, UI, and tests.