josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
awesome-copilot/prompts/create_github_issues_for_unmet_specification_requirements.prompt.md
Daniel Scott-Raynsford 8229a03986 feat: Add comprehensive documentation prompts for OO components, specifications, and .NET best practices 
- Introduced a prompt for creating standardized documentation for object-oriented components, adhering to industry best practices and architectural standards.
- Added a prompt for generating new specification files optimized for Generative AI consumption, including best practices for AI-ready specifications.
- Created a prompt for reviewing .NET/C# code against best practices, focusing on documentation, design patterns, dependency injection, and error handling.
- Developed a prompt for reviewing design pattern implementations in .NET/C# code, providing a checklist and improvement focus areas.
- Implemented a prompt for updating Azure Verified Modules in Bicep files to the latest versions, including a breaking change policy.
- Added a prompt for updating existing implementation plans with new requirements or updates to existing code.
- Created a prompt for updating the llms.txt file to reflect changes in documentation or specifications.
- Developed a prompt for updating markdown file sections with an index/table of files from specified folders.
- Introduced a prompt for updating existing object-oriented component documentation based on current implementation.
- Added a prompt for updating existing specifications based on new requirements or code updates.
2025-07-06 11:01:46 +12:00

1.3 KiB
Raw Blame History

mode description tools
agent Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
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 ${input: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