create-tasks

To convert a PRD into GitHub issues, provide the feature plan file so the system can read it, classify tasks by complexity, and generate structured issue bodies with acceptance criteria via gh CLI commands.

You can create a GitHub epic with linked task issues by providing a complex feature plan; the system determines if an epic is needed, creates the parent issue, and attaches child tasks with references to the original plan.

To break down a feature plan into tasks across different services, the system reads your plan file and derives distributed task issues, automatically applying labels and references to match the architectural layers described.

Yes, it works with the gh CLI by emitting ready-to-run commands and body templates, allowing you to create single issues or full epics with properly linked task issues, labels, and PRD references directly from your plan.

You should generate a single GitHub issue instead of an epic when the feature plan has a narrow scope and low complexity, whereas broader plans spanning multiple layers automatically trigger the creation of a parent epic with linked task issues.