create-github-issues-for-unmet-specification-requirements

Create GitHub Issues for Unmet Specification Requirements

Create GitHub Issues for unimplemented requirements in the specification at ${file}.

Security Constraints

• Shell/Bash execution is not permitted; all operations use declared tools only.
• ${file} must resolve within the repository workspace root; reject paths containing .. or absolute paths outside the workspace before reading.

Process

1. Security Check: Verify that the path for ${file} does not contain directory-traversal sequences (../) and does not resolve to an absolute path outside the current repository workspace. If the path fails this check, stop immediately and report the issue to the user without reading any files.
2. Analyze specification file to extract all requirements.
3. Check codebase implementation status for each requirement.
4. Search existing issues using search_issues to avoid duplicates. Match against requirement IDs in issue titles to prevent creating duplicates.
5. User Confirmation: Report the total number of new issues to be created and a summary of unimplemented requirements found. Ask the user for explicit approval before proceeding. If the user declines, stop and report the summary without creating any issues.
6. If approved, create one new issue per unimplemented requirement using create_issue.
7. Use the feature_request.yml template where available; if it does not exist, inform the user and fall back to the default template only with user awareness.

Requirements

• One issue per unimplemented requirement from specification
• Clear requirement ID and description mapping
• Include implementation guidance and acceptance criteria
• Verify against existing issues before creation; include the requirement ID in the issue title to aid future duplicate detection

Issue Content

• Title: Requirement ID and brief description
• Description: Detailed requirement, implementation method, and context
• Labels: feature, enhancement (as appropriate, applied only if labels exist in the target repository)

Implementation Check

• Search codebase for related code patterns
• Check related specification files in /spec/ directory
• Verify requirement isn't partially implemented