|
| 1 | +name: "✨ Feature request" |
| 2 | +description: "Suggest a feature or improvement. Fields below feed a draft OpenSpec proposal." |
| 3 | +title: "[FEATURE] " |
| 4 | +labels: ["enhancement", "feature", "needs-triage"] |
| 5 | +type: "Feature" |
| 6 | +body: |
| 7 | + - type: markdown |
| 8 | + attributes: |
| 9 | + value: | |
| 10 | + ## Suggest a feature |
| 11 | +
|
| 12 | + Thanks for telling us what you need. **Triage happens within 24 hours.** |
| 13 | +
|
| 14 | + The fields below feed an OpenSpec proposal directly if the suggestion |
| 15 | + is accepted. The more concrete you are, the faster it ships. |
| 16 | +
|
| 17 | + Prefer Dutch? Vul de velden in het Nederlands in — that's fine, we triage in both. |
| 18 | +
|
| 19 | + - type: textarea |
| 20 | + id: problem |
| 21 | + attributes: |
| 22 | + label: "Problem" |
| 23 | + description: "What can't you do today? What's the friction? Write it from your perspective — one or two sentences is plenty." |
| 24 | + placeholder: "I want to filter contacts by last interaction date but the list view doesn't support it. I end up exporting to CSV and sorting in a spreadsheet." |
| 25 | + validations: |
| 26 | + required: true |
| 27 | + |
| 28 | + - type: textarea |
| 29 | + id: proposed-solution |
| 30 | + attributes: |
| 31 | + label: "Proposed solution" |
| 32 | + description: "How would you like it to work? Sketches, links, references welcome. \"I'm not sure\" is also a valid answer — we'll figure it out together." |
| 33 | + placeholder: "A date-range filter in the contacts list sidebar, defaulting to last 30 days, persisted per user." |
| 34 | + validations: |
| 35 | + required: true |
| 36 | + |
| 37 | + - type: textarea |
| 38 | + id: who-benefits |
| 39 | + attributes: |
| 40 | + label: "Who benefits" |
| 41 | + description: "Which user role or workflow does this serve? Be specific." |
| 42 | + placeholder: "Account managers tracking client engagement, especially before renewal conversations." |
| 43 | + validations: |
| 44 | + required: true |
| 45 | + |
| 46 | + - type: dropdown |
| 47 | + id: priority-to-you |
| 48 | + attributes: |
| 49 | + label: "How important is this to you?" |
| 50 | + description: "Honest self-assessment. Helps us prioritise." |
| 51 | + options: |
| 52 | + - "Nice to have" |
| 53 | + - "Would use weekly" |
| 54 | + - "Would use daily" |
| 55 | + - "Blocking me right now" |
| 56 | + validations: |
| 57 | + required: true |
| 58 | + |
| 59 | + - type: textarea |
| 60 | + id: context |
| 61 | + attributes: |
| 62 | + label: "Anything else?" |
| 63 | + description: "Edge cases, alternatives you've considered, things to avoid, related capabilities, anything that didn't fit in the boxes above." |
| 64 | + placeholder: "Out of scope: per-team default filter (could be later). Avoid: hiding the filter behind a settings page — needs to be one click from the list." |
| 65 | + |
| 66 | + - type: markdown |
| 67 | + attributes: |
| 68 | + value: | |
| 69 | + ### Context |
| 70 | +
|
| 71 | + The fields below are auto-filled when you suggest a feature from inside |
| 72 | + the app. They capture where you were when the idea hit so we can scope |
| 73 | + the spec without a second round of questions. |
| 74 | +
|
| 75 | + **We show them to you here on purpose**: you can see exactly what we |
| 76 | + send and edit or clear any field before you submit. Leave them blank if |
| 77 | + you're filing directly from GitHub — we'll still triage it. |
| 78 | +
|
| 79 | + - type: input |
| 80 | + id: app |
| 81 | + attributes: |
| 82 | + label: "App" |
| 83 | + description: "Auto-filled by the in-product modal. The Nextcloud app you were using." |
| 84 | + placeholder: "pipelinq" |
| 85 | + |
| 86 | + - type: input |
| 87 | + id: page |
| 88 | + attributes: |
| 89 | + label: "Page" |
| 90 | + description: "Auto-filled. The manifest page id + route you were on when you opened the modal." |
| 91 | + placeholder: "clients-detail (/clients/abc-123)" |
| 92 | + |
| 93 | + - type: input |
| 94 | + id: surface |
| 95 | + attributes: |
| 96 | + label: "Modal or widget" |
| 97 | + description: "Auto-filled. Any modal, dialog, dashboard widget, or sidebar tab open at the moment the modal launched. Helps us pinpoint UI-attached suggestions." |
| 98 | + placeholder: "edit-client-modal · or · dashboard widget: open-leads" |
| 99 | + |
| 100 | + - type: input |
| 101 | + id: object |
| 102 | + attributes: |
| 103 | + label: "Object in focus" |
| 104 | + description: "Auto-filled. The OpenRegister register + schema + UUID the page was viewing, if any. Lets us trace the suggestion to a real data shape." |
| 105 | + placeholder: "pipelinq · Client · 2f9d-…-abc" |
| 106 | + |
| 107 | + - type: input |
| 108 | + id: spec-ref |
| 109 | + attributes: |
| 110 | + label: "Related capability" |
| 111 | + description: "Auto-filled if the page or widget declares a `specRef`. Connects the suggestion to the existing OpenSpec for that capability." |
| 112 | + placeholder: "client-management" |
| 113 | + |
| 114 | + - type: markdown |
| 115 | + attributes: |
| 116 | + value: | |
| 117 | + --- |
| 118 | +
|
| 119 | + ### What happens next |
| 120 | +
|
| 121 | + 1. **Within 24 hours**: a maintainer reads this and replies with one of `ready-to-build`, `needs-design`, `parking-lot`, or `wont-build` (with a reason). |
| 122 | + 2. **If `ready-to-build`**: an OpenSpec proposal is auto-drafted from these fields. Hydra picks it up and opens a draft PR within days. |
| 123 | + 3. **When it ships**: you're credited on the spec, you get a `Co-Authored-By:` trailer on the merge commit, and you appear on the app's contributors page. |
| 124 | +
|
| 125 | + Read the full flow at the [Users are the moat](https://docs.conduction.nl/strategy/users-are-the-moat) strategy doc. |
0 commit comments