Update feature_request.md

This commit is contained in:
PSBigBig + MiniPS 2026-03-09 13:45:11 +08:00 committed by GitHub
parent 4c2bd6389e
commit 7aa1f4dc80
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -1,20 +1,80 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: ''
assignees: ''
description: Suggest a meaningful improvement to the WFGY ecosystem, docs, tooling, or public structure.
title: "[Feature] "
labels:
- enhancement
- needs-triage
body:
- type: markdown
attributes:
value: |
Use this form for meaningful improvements.
---
Good examples:
- a new docs surface
- a better routing layer
- a reusable triage asset
- a public proof improvement
- a better collaboration or contribution flow
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
- type: textarea
id: problem
attributes:
label: What problem does this solve
description: Explain the gap, friction, or limitation first
placeholder: Describe the problem clearly
validations:
required: true
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
- type: textarea
id: proposal
attributes:
label: Proposed improvement
description: Describe the feature, structure, or improvement you want to see
placeholder: Describe the requested improvement
validations:
required: true
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
- type: dropdown
id: area
attributes:
label: Which area does this affect
options:
- Documentation
- Problem Map line
- Public proof layer
- Collaboration layer
- Contribution workflow
- Application layer
- Core framework
- Other
validations:
required: true
**Additional context**
Add any other context or screenshots about the feature request here.
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: Optional. If you considered another path, describe it
placeholder: Describe alternative approaches if relevant
validations:
required: false
- type: textarea
id: context
attributes:
label: Additional context
description: Add links, examples, screenshots, or comparisons if useful
placeholder: Paste extra context here
validations:
required: false
- type: checkboxes
id: checklist
attributes:
label: Checklist
options:
- label: I described the problem before the proposed solution
required: true
- label: I understand this may be re-scoped into docs, recognition, or another workstream after review
required: true