|
| 1 | +name: 💡 Lab idea or learner question |
| 2 | +description: Suggest a new lab, propose a deep-dive topic, or ask a question that could become a future More Lab. |
| 3 | +title: "[idea] " |
| 4 | +labels: ["lab-idea", "triage"] |
| 5 | +body: |
| 6 | + - type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + Thanks for helping shape the workshop! We review these regularly and turn the |
| 10 | + best ones into new **More Labs** (see [`labs/more/`](../tree/main/labs/more)). |
| 11 | +
|
| 12 | + - 🎓 **Learners** — use this to ask a question or suggest a topic you'd like a lab on. |
| 13 | + - 🛠️ **Maintainers** — use this to capture your own lab ideas so they're tracked. |
| 14 | +
|
| 15 | + For in-lab help, activate the [workshop-coach](../blob/main/.github/agents/workshop-coach.agent.md) instead of filing an issue. |
| 16 | +
|
| 17 | + - type: dropdown |
| 18 | + id: kind |
| 19 | + attributes: |
| 20 | + label: What kind of submission is this? |
| 21 | + options: |
| 22 | + - Question I'd like answered as a future lab |
| 23 | + - Idea for a new More Lab (deep-dive) |
| 24 | + - Idea for a new Core Lab (fundamental to the DevOps loop) |
| 25 | + - Improvement to an existing lab |
| 26 | + - Something else |
| 27 | + validations: |
| 28 | + required: true |
| 29 | + |
| 30 | + - type: input |
| 31 | + id: summary |
| 32 | + attributes: |
| 33 | + label: One-line summary |
| 34 | + description: Phrase it as the question the lab would answer, if possible. |
| 35 | + placeholder: "How do I red-team a hosted agent before shipping it?" |
| 36 | + validations: |
| 37 | + required: true |
| 38 | + |
| 39 | + - type: textarea |
| 40 | + id: problem |
| 41 | + attributes: |
| 42 | + label: What problem or scenario does this address? |
| 43 | + description: What is the learner trying to solve? What made you ask? |
| 44 | + placeholder: | |
| 45 | + As a learner who just finished the Core Labs, I want to know how to... |
| 46 | + because in production I expect to face... |
| 47 | + validations: |
| 48 | + required: true |
| 49 | + |
| 50 | + - type: dropdown |
| 51 | + id: loop_node |
| 52 | + attributes: |
| 53 | + label: Which part of the Agent DevOps loop does this touch? |
| 54 | + description: If you're not sure, pick "Not sure". |
| 55 | + options: |
| 56 | + - Plan |
| 57 | + - Build |
| 58 | + - Evaluate |
| 59 | + - Deploy |
| 60 | + - Monitor |
| 61 | + - Optimize |
| 62 | + - Multiple / cross-cutting |
| 63 | + - Not sure |
| 64 | + validations: |
| 65 | + required: true |
| 66 | + |
| 67 | + - type: dropdown |
| 68 | + id: agent_type |
| 69 | + attributes: |
| 70 | + label: Which agent does this apply to? |
| 71 | + options: |
| 72 | + - Prompt Agent |
| 73 | + - Hosted Agent |
| 74 | + - Both |
| 75 | + - Neither / general Foundry topic |
| 76 | + validations: |
| 77 | + required: true |
| 78 | + |
| 79 | + - type: textarea |
| 80 | + id: outcome |
| 81 | + attributes: |
| 82 | + label: What should a learner be able to do after this lab? |
| 83 | + description: Write this as a verifiable outcome. This becomes the lab's `✅ Verify` section. |
| 84 | + placeholder: | |
| 85 | + - Run an adversarial evaluation against my agent |
| 86 | + - Interpret the failure categories |
| 87 | + - Add a mitigation and re-run to see it pass |
| 88 | + validations: |
| 89 | + required: false |
| 90 | + |
| 91 | + - type: textarea |
| 92 | + id: prereqs |
| 93 | + attributes: |
| 94 | + label: Prerequisites the learner should have completed |
| 95 | + description: List labs (e.g., `fundamentals/06-verify`) or concepts. |
| 96 | + placeholder: | |
| 97 | + - fundamentals/06-verify |
| 98 | + - core/02-evaluate-portal |
| 99 | + validations: |
| 100 | + required: false |
| 101 | + |
| 102 | + - type: textarea |
| 103 | + id: references |
| 104 | + attributes: |
| 105 | + label: References, docs, or examples |
| 106 | + description: Links to Microsoft Learn, Foundry docs, blog posts, papers, or code. |
| 107 | + placeholder: | |
| 108 | + - https://learn.microsoft.com/azure/ai-foundry/... |
| 109 | + validations: |
| 110 | + required: false |
| 111 | + |
| 112 | + - type: dropdown |
| 113 | + id: priority |
| 114 | + attributes: |
| 115 | + label: How urgent does this feel to you? |
| 116 | + options: |
| 117 | + - Nice-to-have — someday |
| 118 | + - Would help me soon |
| 119 | + - Blocking me from adopting the workshop |
| 120 | + validations: |
| 121 | + required: true |
| 122 | + |
| 123 | + - type: checkboxes |
| 124 | + id: contribution |
| 125 | + attributes: |
| 126 | + label: Willing to help? |
| 127 | + options: |
| 128 | + - label: I'd be willing to draft this lab or co-author it. |
| 129 | + - label: I'd be willing to review a draft. |
| 130 | + - label: Just filing the idea — no bandwidth to contribute right now. |
| 131 | + |
| 132 | + - type: markdown |
| 133 | + attributes: |
| 134 | + value: | |
| 135 | + --- |
| 136 | + **What happens next?** Maintainers triage `lab-idea` issues on a regular |
| 137 | + cadence, research the top candidates, and promote them to a `labs/more/` |
| 138 | + entry via the flow in [`.github/MAINTAINERS.md`](../blob/main/.github/MAINTAINERS.md). |
0 commit comments