name: Feature request about: Suggest new behavior, a capability gap, or a product improvement. title: "" labels: ["enhancement", "triage"] assignees: []
This project is built in 16 sequential phases (see
ROADMAP.md). A feature request lands in the phase that owns its domain — the label/milestone reflect that. If it is already specced indocs/tasks/, link the task ID instead of re-describing it.
Description
What do you want to happen, in 2-5 sentences? Describe the user-visible outcome, not the implementation.
Motivation
Why does this matter? Who is the user? What job does this let them do that they cannot do today (or only painfully)?
- Use case: …
- Frequency / pain: …
Proposed solution
How should it work? UI sketch, flow, or pseudocode. If you are unsure, say "no strong preference" — the spec decides.
Alternatives considered
Other ways to achieve the same outcome, and why this one is better (or why the alternatives fall short).
Phase estimate (maintainers)
<!-- Fill in during triage, then delete this block from the rendered issue. Map the request to a ROADMAP.md phase; if it spans phases, name the primary one and list the others as dependencies. If it is out of scope for all 16 phases, say so and link the roadmap discussion. -->
- Primary phase:
Phase N — <name>(docs/tasks/phase-NN-<slug>.md) - Dependent phases: …
- MVP? (yes/no + note) — see
PRODUCT-SPEC.md§28 MVP Boundary
Additional context
Links, screenshots, prior art (Notion/Obsidian/Logseq behavior worth matching), and any related issues/PRs.