to-issues

Convert software plans and specifications into detailed GitHub issues.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/dformoso/positronic --skill to-issues-dformoso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/dformoso/positronic/tree/main/skills/defining/to-issues
Command: npx skills add https://github.com/dformoso/positronic --skill to-issues-dformoso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the conversion of software plans, specifications, and PRDs into GitHub issues, streamlining the transition from abstract ideas to actionable tasks.

Core Features & Use Cases

  • Plan to Issues Conversion: Break down software requirements and PRDs into granular GitHub issues.
  • Verification Fidelity: Ensures each issue aligns with the specified verification levels (data, external access, eval signal, CUJ verification, deploy).
  • Increment Reconciliation: Reconciles open issues with the latest specifications, closing or updating outdated items.

Quick Start

Use the to-issues skill to create GitHub issues from the latest specifications in the 'definitions/specs/' directory.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I convert a software project plan or PRD into GitHub issues?

Converting a software project plan into GitHub issues involves analyzing project requirements and breaking down specifications from your PRD into granular, actionable tasks. This ensures structured task creation aligned with project milestones and dependencies.

What is the best way to ensure GitHub issues align with software specifications?

Ensuring GitHub issues align with software specifications requires verification fidelity checks across data, external access, eval signal, CUJ verification, and deploy levels. This validates that each created issue matches the defined project requirements.

How do I reconcile open GitHub issues with updated project specifications?

Reconciling open GitHub issues with updated project specifications involves comparing existing open issues against the latest specs. This process automatically closes or updates outdated items to maintain project traceability and alignment.

Does to-issues work with specifications stored in a local directory?

Yes, to-issues works with specifications stored locally by reading the latest project plans directly from the definitions/specs directory. It uses these local files to generate and update GitHub issues automatically.

How are project milestones and dependencies handled during plan to issues conversion?

During plan to issues conversion, project milestones and dependencies are handled by analyzing the project requirements and structuring the created GitHub issues to align with them. This ensures proper task sequencing and traceability.