vibe-sdlc-issues

Convert finalized development plans into GitHub Issues and linked project boards.

6|3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-sdlc-issues
Source: https://github.com/robin-li/vibe-money-book/tree/main/.claude/skills/vibe-sdlc-issues
Command: npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a finalized development plan and specification documents into structured, trackable GitHub Issues and a linked Project board so tasks become assignable, measurable, and visible in the repo UI.

Core Features & Use Cases

  • Precondition checks: Verifies presence of PRD/SRD/API spec and the Dev Plan before proceeding.
  • Label & Milestone provisioning: Creates standardized priority, milestone, type, role, and review labels and milestones required by the Dev Plan.
  • Issue generation: Transforms each Dev Plan task into a GitHub Issue following a strict template (description, task ID, steps, acceptance criteria, technical references, dependencies, and labels).
  • Verification tasks: Detects all manual verification items and creates dedicated verification Issues assigned to the appropriate reviewer role with ux-review/review/acceptance tags.
  • Project board automation: Optionally creates or links a GitHub Project, adds Issues, and links the Project to the repository to ensure visibility in the Projects tab.
  • Operational safety: Requires gh CLI authentication and explicit developer confirmation before creating or modifying repo artifacts.

Quick Start

Use the skill to create all Issues and an optional Project board from /docs/02-Dev_Plan.md after confirming gh CLI is authenticated and the Dev Plan is finalized.

Frequently Asked Questions about vibe-sdlc-issues

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

FAQPage Schema
How do I convert a dev plan into tracked GitHub Issues and project board entries?

To convert a dev plan into GitHub Issues, the skill parses finalized spec documents and transforms each task into structured Issues with labels, milestones, and acceptance criteria, optionally linking them to a GitHub Project board.

What prerequisites do I need to automate GitHub Issues generation from a markdown dev plan?

Automating GitHub Issues generation requires gh CLI authentication, explicit developer permissions, and the presence of finalized PRD, SRD, and a Dev Plan markdown file in your repository's docs directory.

Does generating GitHub milestones and labels require manual setup before running the automation?

Generating GitHub milestones and labels does not require manual setup; the skill automatically provisions standardized priority, type, role, and review labels alongside required milestones directly from the dev plan.

Can I automatically assign verification issues to specific reviewers from my development plan?

Yes, you can automatically assign verification issues. The skill detects manual verification items in the dev plan and creates dedicated issues assigned to the appropriate reviewer role with ux-review or acceptance tags.

How does linking a GitHub Project board to my repository work when creating issues?

Linking a GitHub Project board happens automatically after issue creation. The skill optionally creates or links a Project, adds the generated issues, and connects the board to your repository to ensure visibility in the Projects tab.

What happens if my repository does not contain the required PRD or API spec files?

If your repository does not contain the required PRD, SRD, or Dev Plan files, the skill terminates during precondition checks to prevent generating incomplete issues, ensuring all specification documents exist before proceeding.