to-issues

Converts plans, specs and PRDs into dependency-ordered tracer-bullet vertical slice issues for a project tracker.

195|16|Updated Feb 18, 2025
One-click install
npx skills add https://github.com/InditexTech/weavejs --skill to-issues-inditextech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/InditexTech/weavejs/tree/main/code/.agents/skills/to-issues
Command: npx skills add https://github.com/InditexTech/weavejs --skill to-issues-inditextech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down complex plans, specs, or PRDs into independently actionable issues on your tracker, enabling clearer scope and faster delivery.

Core Features & Use Cases

  • Converts plans into tracer-bullet vertical slices that map to end-to-end work
  • Creates implementation tickets with traceability from high-level goals to concrete tasks
  • Use Case: A product manager converts a PRD into a set of issues for sprint planning and triage

Quick Start

Feed your plan, and let the system generate tracer-bullet issues in the project tracker.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I break down a PRD into trackable issues for sprint planning?

Tracer-bullet vertical slices divide a project plan into independently trackable end-to-end issues, enabling clearer scope and faster delivery across multiple teams.

What are tracer-bullet vertical slices in issue tracking?

Tracer-bullet vertical slices divide a project plan into independently trackable end-to-end issues, enabling clearer scope and faster delivery across multiple teams.

How do I create dependency-ordered implementation tickets from a project spec?

To break down a PRD into trackable issues, feed the plan into the system to automatically generate tracer-bullet vertical slices mapped to end-to-end work on your project tracker.

Do I need an existing issue tracker to convert plans into vertical slices?

Create dependency-ordered implementation tickets by submitting the spec for context gathering, slice drafting, and automated publishing to generate traceable tasks from high-level goals.

Can I use this approach to track end-to-end work across multiple teams?

Yes, you need access to an issue tracker and a labeled vocabulary to publish dependency-ordered issues and enable end-to-end tracking across multiple teams.