plan-to-issues

To automate GitHub issues from architecture plans, this Skill parses structured documents to extract sprints, tasks, acceptance criteria, and gates, then generates corresponding milestones and issues in your repository. It requires an agent-mapping file and GitHub CLI access.

The architecture plan must follow the specific format described in the PARSER.md document for successful GitHub issue generation. This structured format allows the parser to accurately extract sprints, tasks, acceptance criteria, and gates for milestone creation.

Yes, you can generate GitHub milestones for sprint planning directly from a structured architecture document. The automation extracts sprint sections and creates matching milestones, task issues, and gate verification issues in the target repository.

Yes, an agent-mapping file is required to create GitHub issues from a plan. This file drives the workflow to assign primary agents and skills, applying templates to ensure consistent documentation across the generated task and gate verification issues.

Parsing acceptance criteria and gates into GitHub issues is handled by extracting these specific sections from your structured architecture plan. The automation then creates dedicated gate verification issues and task issues in the target GitHub repository.

Yes, plan-to-issues works directly with the GitHub CLI for repository automation. It requires GitHub CLI access to automatically generate milestones, task issues, and gate verification issues in the target repository from your architecture plans.