issue-planner

To turn a Markdown project plan into a GitHub backlog, you can use a skill that parses design and build-out plan Markdown files to generate a structured batch of GitHub issues. This process requires an authenticated GitHub CLI environment with project scope permissions to execute API-driven issue creation.

Yes, you can automatically create a GitHub project board from design documents. The parsing process generates GitHub issues and simultaneously creates and populates a corresponding project board to visualize the delivery flow.

Parsing ADRs ensures traceability between architecture decisions and work items. The parsing mechanism extracts requirements from Markdown plans to create GitHub issues with appropriate labels and milestones, linking project requirements consistently.

Yes, you need an authenticated GitHub CLI environment with project scope permissions to generate issues from a project plan. This authenticated setup is required to execute the API-driven issue and project board creation successfully.

The best way to structure a Markdown plan for automated GitHub issue generation is to organize it by project phases, requirements, and milestones. The parsing tool targets software and research projects requiring disciplined delivery flows, translating structured Markdown into appropriately labeled issues.

GitHub issues may not link to the correct project phases if the Markdown plan lacks structured formatting for milestones or if the GitHub CLI environment lacks sufficient project scope permissions. Consistent Markdown structuring ensures requirements are accurately translated into tracked work items.