b0-conversation-to-issues

Convert conversations or PRDs into structured GitHub issues with dependency-managed tasks.

6|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/jporre/sveltekit-verticalslices --skill b0-conversation-to-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b0-conversation-to-issues
Source: https://github.com/jporre/sveltekit-verticalslices/tree/main/skills/b0-conversation-to-issues
Command: npx skills add https://github.com/jporre/sveltekit-verticalslices --skill b0-conversation-to-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, AskUserQuestion, Agent, Workflow, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill converts verbal or written conversations, plans, or PRDs into detailed, structured GitHub issues. It helps organize tasks and track progress in a project by slicing conversations into manageable vertical slices.

Core Features & Use Cases

  • Conversational Issue Creation: Transforms discussions into issues with clear objectives, entities, and operations.
  • Vertical Slicing: Organizes tasks into vertical slices that represent end-to-end functionality.
  • Dependency Tracking: Ensures that issues are created in a logical order, with dependencies properly managed.
  • Use Case: Ideal for project planning sessions or brainstorming meetings where tasks need to be broken down into actionable items.

Quick Start

Use the 'b0-conversation-to-issues' skill to create GitHub issues from the current conversation.

Frequently Asked Questions about b0-conversation-to-issues

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

FAQPage Schema
How do I convert a project conversation or PRD into structured GitHub issues?

To convert conversations or PRDs into GitHub issues, the Skill analyzes textual discussions to identify domain entities and operations, then slices them into vertical, dependency-managed tasks before outputting a JSON plan for issue creation.

What is vertical slicing when creating GitHub issues from planning sessions?

Vertical slicing organizes tasks from conversations into end-to-end functional units, ensuring each GitHub issue represents a complete feature slice with properly tracked dependencies for logical implementation order.

Can I use conversation analysis to automatically track task dependencies in GitHub?

Yes, conversation analysis automatically tracks task dependencies by evaluating domain restrictions and operations within your plans, ensuring GitHub issues are generated in a logical sequence with managed dependencies.

How do I break down brainstorming meeting notes into actionable GitHub tasks?

Breaking down meeting notes into actionable tasks requires analyzing the conversation for core objectives and entities, slicing the content into manageable vertical tasks, and confirming the plan before generating GitHub issues.

Does this issue creation approach work with existing project plans and requirements documents?

Yes, this approach works with existing project plans and requirements documents by processing any textual conversation or PRD to extract domain operations and entities, yielding structured GitHub issues ready for tracking.

Do I need to confirm the GitHub issue plan before the actual issue creation happens?

Yes, user confirmation is required after the conversation analysis phase and before the final output, ensuring the proposed vertical slices, domain entities, and dependency sequences accurately match your project intent.