Feature Spec

Turn a feature request into a scoped, buildable spec with a clear success measure.

tinyhumansai Updated

File contents

Feature Spec

Take a raw request and shape it into a spec engineering can build and everyone agrees on.

When to use

  • A feature is greenlit and needs definition before work starts.
  • A vague request needs scoping before it can be estimated.

Steps

  1. State the problem and the user it is for, not the solution.
  2. Define the scope: what is in, what is explicitly out.
  3. Describe the flows and the key states and edge cases.
  4. Set the success measure and how it will be checked.
  5. Flag risks, dependencies, and open questions for the operator.

Output

A spec: problem, scope, flows, success measure, and open questions — following the [[Engineering standards]]. Ready to estimate and build.

tinyhumansai/opencompany/tree/main/companies/software_company/skills/feature-spec commit 5929fbafa8

Frequently asked questions

npx skillmds@latest add tinyhumansai/feature-spec