sharang
ebf627372f
Adds the §1.2 scaffolding required by IMPLEMENTATION_PLAN.md M0.1: README, CONTRIBUTING, CODEOWNERS, CHANGELOG, PR + issue templates, CI workflow, release workflow, LICENSE, commitlint, cliff config, .editorconfig, .gitignore, .env.example. Refs: M0.1
42 lines
1002 B
Markdown
42 lines
1002 B
Markdown
---
|
||
name: Feature / change request
|
||
about: Propose a new capability or behavior change
|
||
labels: enhancement
|
||
---
|
||
|
||
## Problem
|
||
|
||
<!-- What is the customer / operator / developer trying to do today, and why is it painful?
|
||
Lead with the WHY. -->
|
||
|
||
## Proposed solution
|
||
|
||
<!-- One paragraph. The shape of the change, not the implementation detail. -->
|
||
|
||
## Acceptance criteria
|
||
|
||
<!-- A reviewer should be able to read these and say "shipped" or "not shipped". -->
|
||
|
||
- [ ]
|
||
- [ ]
|
||
- [ ]
|
||
|
||
## Alternatives considered
|
||
|
||
<!-- 1–2 sentences each. "Do nothing" is always one alternative — say why it's worse. -->
|
||
|
||
## Linked milestone
|
||
|
||
<!-- Optional. If this maps to an existing milestone in IMPLEMENTATION_PLAN.md, link it.
|
||
If it doesn't, that's a signal the plan needs an update. -->
|
||
|
||
M1.1 — or **new milestone needed**
|
||
|
||
## Out of scope
|
||
|
||
<!-- Things this issue explicitly does NOT cover, so reviewers don't expand the scope. -->
|
||
|
||
## Open questions
|
||
|
||
<!-- Things to resolve before implementation can start. -->
|