Some New Feature — Brief

A short, plain-language statement of what this feature is and why it exists. The brief is the first doc in every feature folder under the feature-driven spec.

What it is

One or two sentences describing the feature in user-facing terms. Avoid jargon, implementation details, or technical scope — those go in the plan.

Why we need it

The motivation. Often a user pain point, a missing capability, a constraint from another team, or a strategic bet.

What success looks like

• A specific, observable outcome
• Another observable outcome
• A non-goal you're explicitly not trying to solve

Open concerns

Anything you already know is tricky and want to flag before you start planning. The plan resolves these; the implementation closes them.

Tip This is the first doc to exist. You can publish a feature folder with just a brief and grow into plan / implementation later — the engine shows whichever docs exist.