Verified:GitHub

plan-to-issues

Project a markdown plan into GitHub issues and Projects.

1|Updated Jan 22, 2026

Search Tags:#github issues #project board #dry-run #workstreams #automation manifest #issue projection #planning to execution

Ready to run

npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill plan-to-issues-atlas-memory-framework

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-to-issues
Source: https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools/tree/main/.cursor/skills/plan-to-issues
Command: npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill plan-to-issues-atlas-memory-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires argparse, PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It turns a single markdown plan artifact into a coherent set of GitHub tracking objects (issues and optional GitHub Projects) so you can move from planning to execution without letting downstream surfaces become the new authority.

Core Features & Use Cases

Dry-run previews first: generate proposed epics and child issues (including labels, points, dependencies, blockers, merge points, and validation requirements) before making any GitHub writes.
Strategy-driven projection: support workstreams, phases, or leaf-issue story breakdown via the Automation Issue Manifest when present.
Idempotent-style sync: update issue bodies/labels to match the current plan while avoiding destructive operations like closing/deleting issues unless explicitly requested.
GitHub Project wiring: create or use a GitHub Project and add created issues to the correct project board when tracking is requested.

Quick Start

Ask to run plan-to-issues in dry-run mode for your selected plan artifact and include the target repository so you can review the proposed epic and child issues before applying.

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 a markdown plan into GitHub issues for execution tracking?▼

To convert a markdown plan into GitHub issues, you project the plan artifact into epics and child issues while preserving the original plan as the authoring authority. This ensures the markdown remains the source of truth for execution tracking.

Can I preview GitHub issues from a markdown plan before writing them to a repository?▼

Yes, you can preview GitHub issues by running the projection in dry-run mode. This generates proposed issues with labels, dependencies, and validation requirements before any GitHub writes occur to your repository.

How do I break down a project plan into GitHub workstreams and phases?▼

You break down a project plan into GitHub workstreams and phases using an Automation Issue Manifest if present. This strategy-driven projection maps the plan structure into workstreams, phases, or leaf-issue story breakdowns for execution.

Does syncing markdown plans to GitHub issues close or delete existing issues automatically?▼

No, syncing markdown plans to GitHub issues does not close or delete existing issues automatically. The idempotent-style sync updates issue bodies and labels to match the current plan while avoiding destructive operations unless explicitly requested.

How do I add created GitHub issues to a project board automatically?▼

You add created GitHub issues to a project board automatically by requesting GitHub Project wiring during the projection. This creates or uses an existing GitHub Project and routes generated issues to the correct project board for execution tracking.