coding-feature-spec

To create a behavior contract, you need to read repository context, identify user goals and edge cases, and document accepted behavior alongside non-goals. This produces a decision-complete contract that reduces ambiguity before implementation starts.

Feature specification is the process of defining intended software behavior before building it. It involves requirements discovery, edge-case challenge, and explicit behavior decisions to ensure a non-trivial repository change is fully understood prior to coding.

Write a feature specification by analyzing the repository context, challenging edge cases, and finalizing behavior decisions. This generates a focused FEATURE.md document that captures the agreed behavior and unresolved items without requiring approval gates.

You need a behavior-first workflow when a non-trivial software feature requires user discovery and explicit behavior decisions before implementation. It is essential when requests are vague and reducing rework through a decision summary is critical.

The best way to document non-goals and edge cases is to capture them in a concise decision summary. This acts as a behavior contract, ensuring unresolved items and agreed limitations are explicitly defined before handing off to proof authoring.