Feature
Describe a user-visible outcome and the evidence that will prove it works.
Purpose
Describe a user-visible outcome and the evidence that will prove it works.
Recommended
- State the goal, relevant context, constraints, and observable acceptance criteria.
- Name validation commands and compatibility requirements.
- Distinguish required behavior from optional refinements.
Avoid
- Asking the model to invent missing product decisions.
- Treating implementation activity as proof of the user outcome.
Prompt skeleton
Prompt skeleton — deterministic, no model call
Goal [State the user-visible outcome.] Context and constraints [Include relevant files, boundaries, and compatibility requirements.] Acceptance criteria [List observable completion conditions.] Validation [Name the checks that should pass.]
From templates/feature.md. Placeholders describe what to fill in; nothing here invents project facts.
Evidence
official
- officialStructured feature-request fields help contributors provide specific information.
Configuring issue templates for your repository ↗