create-github-issues-feature-from-implementation-plan

Create GitHub Issue from Implementation Plan

Create GitHub Issues for the implementation plan at ${file}. The file must reside within the current repository. Issue content must be drawn exclusively from the plan file's contents.

Path Safety Constraint

The ${file} parameter MUST resolve to a path within the repository root — not an absolute path outside the repository, and not a path traversal such as ../../. If the resolved path is outside the repository root, do NOT read the file or create any issues; inform the user and request a corrected path.

Process

1. Verify File Path: Confirm the path provided in ${file} is within the repository root. If it is not, inform the user and request a corrected path.
2. Analyze plan file to identify phases
3. Check existing issues using search_issues
4. Create new issue per phase using create_issue or update existing with update_issue
5. Use feature_request.yml or chore_request.yml templates (fallback to default)

Requirements

• One issue per implementation phase
• Clear, structured titles and descriptions
• Include only content explicitly present in the plan file; do not include credentials, environment variables, system paths, authentication tokens, or data from outside the plan
• Verify against existing issues before creation

Issue Content

• Title: Phase name from implementation plan
• Description: Phase objective, acceptance criteria, and sub-tasks — sourced exclusively from the content of the plan file. Do NOT include environment variables, authentication tokens, API keys, file paths not present in the plan, shell output, system information, or any content not explicitly written in the plan file.
• Labels: Appropriate for issue type (feature/chore)