Set Up GitHub Issue Templates for the Vets Who Code App

[jeromehardaway]

🧠 Context
To streamline how we collaborate, track bugs, and propose new features in the Vets Who Code app, we need to establish a formal issue template system. This will improve clarity and ensure consistent structure across all contributor submissions — especially important as we expand work across features like the PTSD Toolkit and AEGIS dashboard.

✅ Acceptance Criteria
• Create a .github/ISSUE_TEMPLATE/ directory at the root of the repository
• Add the following issue templates as Markdown files:
• task.md for general implementation work
• bug_report.md for identifying and resolving defects
• feature_request.md for proposing new capabilities
• Use YAML frontmatter to define name, about, labels, assignees, and title patterns
• (Optional) Add config.yml to disable blank issues and encourage structured input
• Validate that the new templates appear correctly at /issues/new/choose on GitHub

🧪 Implementation Plan
1. Create the .github/ISSUE_TEMPLATE/ folder
2. Add Markdown files with appropriate frontmatter and prompts
3. Commit and push to main
4. Test issue creation via /issues/new/choose to ensure templates render
5. Refactor or expand templates later as needed (e.g. documentation request, internal-only)

🛠️ Resources
• GitHub Docs: Configuring Issue Templates
• Template examples: see previous chat or request .zip packaging

📎 Additional Notes
This is the foundation for a consistent contributor experience and sets the tone for our engineering culture as we grow. Templates should reflect our emphasis on clarity, actionability, and asynchronous productivity.