2b45ca4e8b
- Replace 'codebase' with 'search/codebase' - Replace 'searchResults' with 'search/searchResults' - Replace 'terminalLastCommand' with 'runCommands/terminalLastCommand' - Replace 'terminalSelection' with 'runCommands/terminalSelection' Updated files: - 13 chatmode files in chatmodes/ - 41 prompt files in prompts/ This update aligns with VS Code's latest tool naming conventions that organize tools into logical namespaces.
36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
---
|
|
mode: 'agent'
|
|
description: 'Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.'
|
|
tools: ['search/codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
|
|
---
|
|
# Create GitHub Issues for Unmet Specification Requirements
|
|
|
|
Create GitHub Issues for unimplemented requirements in the specification at `${file}`.
|
|
|
|
## Process
|
|
|
|
1. Analyze specification file to extract all requirements
|
|
2. Check codebase implementation status for each requirement
|
|
3. Search existing issues using `search_issues` to avoid duplicates
|
|
4. Create new issue per unimplemented requirement using `create_issue`
|
|
5. Use `feature_request.yml` template (fallback to default)
|
|
|
|
## 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
|
|
|
|
## Issue Content
|
|
|
|
- Title: Requirement ID and brief description
|
|
- Description: Detailed requirement, implementation method, and context
|
|
- Labels: feature, enhancement (as appropriate)
|
|
|
|
## Implementation Check
|
|
|
|
- Search codebase for related code patterns
|
|
- Check related specification files in `/spec/` directory
|
|
- Verify requirement isn't partially implemented
|