Capture Future Improvements & Ideas as GitHub Issues

[jdsika]

Objective:
Ensure that all future improvements, ideas, and feature requests are documented as GitHub issues in the repository. Prevent loss of valuable input by centralizing discussions and tracking progress transparently.

---

Tasks:

1. Create a Process for Idea Capture:

   • Encourage team members to immediately open a GitHub issue for any new idea, improvement, or bug fix.
   • Use the "Idea" or "Enhancement" label for non-critical suggestions.

2. Standardize Issue Format:

   • Each issue should include:
     • Clear title (e.g., "Add Support for Batch Credential Verification").
     • Description (purpose, scope, and expected outcome).
     • Optional: Mockups, code snippets, or references (e.g., Miro, discussions).
   • Example:

     ### Description
     Extend the Verifier service to support batch verification of 10+ credentials in a single transaction.
     
     ### Rationale
     Reduces gas costs and improves UX for bulk operations.
     
     ### References
     - [Miro Wireframe](#)
     - Related: #123

3. Triage and Prioritize:

   • Assign a team member to review new issues weekly and:
     • Add labels (e.g., priority-high, needs-design).
     • Link to epics or milestones (if applicable).
     • Close duplicates or out-of-scope items with a clear explanation.

4. Document the Workflow:

   • Update CONTRIBUTING.md with a section like:

     ## Sharing Ideas
     1. Open an [issue](https://github.com/ASCS-eV/on-chain-ssi/issues) with the "Enhancement" label.
     2. Use the template to describe your proposal.
     3. The team will review and prioritize it within 7 days.

5. Communicate the Process:

   • Announce the new workflow in team chats/standups.
   • @mention relevant members in critical issues (e.g., @team/backend for API changes).

---

Acceptance Criteria:
✅ All new ideas/improvements are captured as GitHub issues within 24 hours of discussion.
✅ Issues follow the standardized format and include necessary context.
✅ CONTRIBUTING.md is updated with the workflow.
✅ Team members acknowledge the process in a standup or chat.

---

Notes:

• Use milestones to group related ideas (e.g., "Q3 2026 Roadmap").
• For time-sensitive ideas, add a deadline: note in the issue description.
• Example labels to create: needs-discussion, blocked, quick-win.