Pre-built Scenario Templates
- Anton Velychko
Get started quickly with a set of pre-defined scenarios for common tasks such as requirement refinement, solution brainstorming, code implementation suggestions, and test case generation.
There are 9 pre-build scenarios and 13 scenario versions available in-app:
Scenario name | Versions | Short description | |
|---|---|---|---|
| 1 | Advice |
| Some advice on how to improve the existing issue description |
| 2 | Alternatives |
| Get alternatives to the proposed Jira ticket solution to the problem |
| 3 | Code |
| Create some sketch code* implementation of the issue (if applicable). *adding context used in the project tech stack will improve response quality |
| 4 | Just do it |
| Define a task and propose solution to it from the Jira issue |
| 5 | Reasoning |
| Define the problem, evaluate how the changes will impact users, define KPIs |
| 6 | Requirements |
| Extending issue description with additional useful details for requirements |
| 7 | Summary |
| Get options for issue summary that will describe it the best |
| 8 | Test cases |
| Get a list of potential test cases to check/think about before releasing feature |
| 9 | Work plan |
| Building initial roadmap of completing the issue |
Think of scenarios as folder names and scenario versions as their content files. Just an idea - feel free to do your own thing. The version names in the app intentionally follow different patterns to demonstrate various name strategies that may be applied to your needs.
Â