plan-issue

To convert a GitHub issue into an implementation checklist, this skill reads feature specifications from issues labeled has-spec and generates ordered, file-level tasks. It outputs concrete file changes sequenced by dependency for direct execution.

Yes, you can use local markdown spec files for codebase task generation through local mode. This dual-mode support processes local specifications identically to GitHub Issues, producing file-level implementation checklists.

Breaking down feature specifications relies on an internal review loop that catches vague tasks and misordered dependencies. It validates specs and generates ordered, file-level implementation tasks grouped by dependency for accurate sequencing.

Yes, plan-issue validates specs before generating an implementation checklist by running entry gate checks. This prevents duplicate checklists and ensures the specification is fully ready for implementation before proceeding.

If your spec contains vague tasks or misordered dependencies, the internal quality assurance loop catches these issues. It refines the specification breakdown to ensure concrete actionable items and correct task sequencing before approval.

To avoid duplicate checklists when planning GitHub issues, the skill applies built-in entry gate validation. This mechanism checks existing checklists against the current spec before generating new file-level implementation tasks.