prd-to-issues

Convert PRD sections into dependency-ordered GitLab issues with tracer bullets.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/stevenengland/sten-agent-skills --skill prd-to-issues-stevenengland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/stevenengland/sten-agent-skills/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/stevenengland/sten-agent-skills --skill prd-to-issues-stevenengland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a PRD into independently-grabbable GitLab issues using tracer-bullet vertical slices, turning high-level product specs into concrete work items you can assign, estimate, and track.

Core Features & Use Cases

  • Vertical slicing: Convert PRD sections into end-to-end slices that cover schema, API, UI, and tests.
  • Tracer bullets: Each slice traces back to a PRD requirement for traceability.
  • Planning workflow: Generates a sequence of issues in dependency order to guide delivery and planning.

Quick Start

Provide the PRD reference to generate tracer-bullet slices and create corresponding GitLab issues.

Frequently Asked Questions about prd-to-issues

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

FAQPage Schema
How do I break a PRD into actionable GitLab issues?

To break a PRD into actionable GitLab issues, provide a PRD reference number or URL and a GitLab project context. The tool generates end-to-end vertical slices across schema, API, UI, and tests, ordered by dependencies.

Do I need an existing PRD document to generate GitLab issues?

Yes, you need an existing PRD document to generate GitLab issues. You must provide a specific PRD reference, either as a number or a URL, along with your GitLab project context for the vertical slice generation to work.

Can I convert PRD sections into vertical slices for implementation planning?

Yes, you can convert PRD sections into vertical slices for implementation planning. The tool breaks high-level product specs into end-to-end slices that cover schema, API, UI, and tests, generating a sequence of issues in dependency order.

Does the generated issue sequence account for dependencies across layers?

Yes, the generated issue sequence accounts for dependencies across layers. The tool orders the end-to-end vertical slices by their dependencies to guide delivery planning and ensure proper implementation sequencing.

What's the best way to convert high-level product specs into trackable work items?

The best way to convert high-level product specs into trackable work items is using tracer-bullet vertical slicing. This approach turns PRD sections into independently-grabbable issues that you can assign, estimate, and track in GitLab.