How are the questions laid out? For eg, are they what > why > how or what > how > why, or something else?
The idea here is to allow the template form to aid in the thinking of the issue opener
N/A
Team Readability
What does the issue look like once submitted? Will that be readable enough for the team to get started thinking about the issue?
In terms of ease of collaboration, discussions by github provide a much more flexible space for discussing / having open-ended moonshot conversations.
Shortcut Connectivity
How is this issue connected with shortcut? Make sure to list all side-effects!
GitHub says, Discussions are a place for open ended conversations until they are ready to become issues and be tracked. In that context, the connectivity to shortcut for this specific template (ie, moonshot) is downstream.
Notes to keep in mind
What are some shortcomings or nuances that one must be aware of when they are opening, or reading, this issue?
A template around this may be useful if we want to use issues to track epics. Other communities may also benefit from the extensive templates.
Further Work
Is there something thats left to be addressed once this PR is merged? Are there any blockers?
Core Objectives
This template is deleted in favor of discussions. See https://github.com/shil-me/stubs-dao/issues/10
Questioning Strategy
N/A
Team Readability
In terms of ease of collaboration, discussions by github provide a much more flexible space for discussing / having open-ended moonshot conversations.
Shortcut Connectivity
GitHub says, Discussions are a place for open ended conversations until they are ready to become issues and be tracked. In that context, the connectivity to shortcut for this specific template (ie, moonshot) is downstream.
Notes to keep in mind
Further Work
Yes, https://github.com/shil-me/stubs-dao/issues/10