skills.rest
marcmontecalvo
marcmontecalvoCOMMUNITY
Explore all skills by this author →
GitHub

plan-to-issues

Convert planning documents into GitHub EPICs and deterministic child issues aligned to ADRs, specs, and repository paths.

Updated Apr 14, 2026
Search Tags:#planning#templates#github#adr#issues#epic#specs
One-click install
npx skills add https://github.com/marcmontecalvo/waywarden --skill plan-to-issues-marcmontecalvo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-to-issues
Source: https://github.com/marcmontecalvo/waywarden/tree/main/.agents/skills/plan-to-issues
Command: npx skills add https://github.com/marcmontecalvo/waywarden --skill plan-to-issues-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Normalize planning inputs into deterministic GitHub EPICs and child issues aligned to ADRs and specs.

Core Features & Use Cases

  • Normalize planning docs into EPICs and child issues.
  • Enforce templates and canonical references (ADRs, specs, repo paths).
  • Maintain traceability and prevent drift between planning docs and implementation.

Quick Start

Provide planning docs and this skill will generate a deterministic EPIC with child issues wired to ADRs and specs.

Frequently Asked Questions about plan-to-issues

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

FAQPage Schema
How do I convert planning docs into GitHub epics and issues?▼

To convert planning docs into GitHub epics and issues, you provide your planning documents to generate a deterministic EPIC with ordered child issues aligned to ADRs and repository paths.

What is the best way to link GitHub issues to ADRs and specs?▼

Linking GitHub issues to ADRs and specs is handled by enforcing canonical references during issue creation, ensuring ADRs, specs, and repository paths remain the source of truth for traceability.

How do I prevent drift between planning documents and implementation issues?▼

Preventing drift between planning documents and implementation issues relies on normalizing planning inputs into deterministic child issues, enforcing edition templates, and capturing governance artifacts as ordered, traceable work items.

Can I use planning templates to generate traceable GitHub work items?▼

Yes, you can use planning templates to generate traceable GitHub work items by enforcing edition templates and canonical ADR references, ensuring the generated EPICs and child issues align with repository paths.

Does generating GitHub EPICs from specs require manual repository path mapping?▼

Generating GitHub EPICs from specs does not require manual repository path mapping, as the skill automatically wires deterministic child issues to canonical ADRs and repository paths extracted from planning documents.

Related Skills

Explore More Product & Management Skills→
buenhydenbuenhyden
1

docs-stage-routing

Define a repository-local routing contract for document-generation workflows.

Community
Advanced
intelligentcode-aiintelligentcode-ai
1

github-issues-planning

Create typed GitHub Issues with labels, priorities, and parent-child links.

Official
Advanced
john-data-chenjohn-data-chen
2

github-repo-management

Automate GitHub repository cloning, forking, remotes, and releases.

Community
Advanced
ClementWalterClementWalter
2

GitHub Workflow

Guide GitHub issue workflow with hierarchy, milestones, and automation scripts.

Community
Intermediate