d260c65769
- Created a prompt for .NET/C# best practices to ensure code quality and adherence to standards. - Added a design pattern review prompt for evaluating C#/.NET code implementations. - Introduced prompts for suggesting relevant GitHub Copilot chatmodes and prompts based on repository context. - Developed a prompt for updating Azure Verified Modules in Bicep files to the latest versions. - Implemented a prompt for updating implementation plans with new requirements and features. - Created a prompt for updating the llms.txt file to reflect changes in documentation or specifications. - Added a prompt for updating markdown file indexes with files from specified folders. - Developed a prompt for updating object-oriented component documentation according to best practices. - Created a prompt for updating specification files to align with new requirements and ensure AI-readiness.
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: ['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
|