skills.rest
urban233
urban233COMMUNITY
Explore all skills by this author →
GitHub

blueprint-to-issues

Decomposes architecture specifications into dependency-ordered GitHub issue backlogs with wave planning.

Updated Jul 24, 2026
Search Tags:#decomposition#sprint planning#github issues#backlog#dependency graph#parallelism#architecture spec
One-click install
npx skills add https://github.com/urban233/ntn-ingest --skill blueprint-to-issues-urban233
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blueprint-to-issues
Source: https://github.com/urban233/ntn-ingest/tree/main/.agents/skills/blueprint-to-issues
Command: npx skills add https://github.com/urban233/ntn-ingest --skill blueprint-to-issues-urban233

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a large architecture spec or PRD into an actionable team backlog is slow and error-prone: issues overlap, shared contracts get re-decided inconsistently, and dependencies surface only after work collides. This Skill converts a blueprint into a structured, dependency-ordered GitHub issue backlog that a team can execute in parallel without collisions. ## Core Features & Use Cases - Shared-contracts ledger: Extracts schemas, error taxonomies, authority boundaries, and naming conventions from the blueprint into a locked ledger so no issue re-decides them independently. - Dependency graph and wave planning: Topologically sorts issues into waves, flags critical-path risks, idle capacity, and same-wave contention over shared files or schemas. - Standardized issue files: Generates one markdown file per issue with YAML frontmatter (status, labels, depends-on, contention) plus motivation, scope, non-goals, acceptance criteria, and open questions. - Use Case: Paste a product design document and receive a backlog/ directory containing a shared-contracts ledger, an overview with wave diagram and contention flags, and per-issue files ready to paste into GitHub. ## Quick Start Paste your architecture or product specification and ask to break it down into a dependency-ordered GitHub issue backlog for your team.

Frequently Asked Questions about blueprint-to-issues

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

FAQPage Schema
How do I turn a product spec into GitHub issues?▼

Paste or attach the architecture or product spec, and the Skill decomposes it into issues with motivation, scope, non-goals, acceptance criteria, and dependencies. Output is markdown files you paste into GitHub manually or via gh/API automation.

How do I break down a large architecture document for a team?▼

The Skill extracts a shared-contracts ledger first, then slices the blueprint into issues tagged by component, size, and tier. It builds a dependency graph, sorts issues into waves, and flags contention so developers can work in parallel without collisions.

Does this publish issues directly to GitHub?▼

No. Output is markdown only, saved to a backlog/ directory with one file per issue. You paste issues into GitHub manually or automate creation later with gh or the GitHub API.

What inputs does the blueprint decomposition require?▼

It requires the blueprint document itself, pasted or attached in the conversation. If no document is present, the Skill asks for it and waits; the document is the sole source of truth for contracts, issues, and dependencies.

How are issue dependencies and parallel work waves determined?▼

Each issue lists blocking issues, and a topological sort assigns issues to waves: Wave 0 has no dependencies, and each later wave depends only on earlier ones. Same-wave collisions over shared files or schemas get contention flags or added dependency edges.

What are the limitations of this backlog generation approach?▼

It does not invent decisions the blueprint leaves open; unresolved points become open questions for implementation specs. It also does not manage issue status after generation or integrate with GitHub directly.

Related Skills

Explore More Product & Management Skills→
codetail-aicodetail-ai

pm

Creates structured PRDs with user stories, acceptance criteria, and scope boundaries.

Official
Advanced
Reading-Advantage-ThailandReading-Advantage-Thailand

issue-executor

Generates implementation plans for GitHub issues and creates feature branches using the Gemini CLI.

Official
Intermediate
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate
cosmicdreamscosmicdreams

jira

Manage Jira issues, transitions, comments, and sprint views via jira-cli.

Community
Intermediate