josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
awesome-copilot/prompts/create_github_issues_feature_from_implementation_plan.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

994 B
Raw Blame History

mode description tools
agent Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
codebase
search
github
create_issue
search_issues
update_issue

Create GitHub Issue from Implementation Plan

Create GitHub Issues for the implementation plan at ${file}.

Process:

  1. Analyze plan file to identify phases
  2. Check existing issues using search_issues
  3. Create new issue per phase using create_issue or update existing with update_issue
  4. 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 changes required by the plan
  • Verify against existing issues before creation

Issue Content:

  • Title: Phase name from implementation plan
  • Description: Phase details, requirements, and context
  • Labels: Appropriate for issue type (feature/chore)