📐 scrumia-specs

What it is responsible for

Owns where a specification lives and what shape it takes: one directory per feature, each file with a defined reader — the business rules, the acceptance criteria, the technical choices, the interface. Creates a feature, updates it, audits it, and finds the one that owns a rule without reading the whole tree.

What it refuses

No fixed template, no history inside a spec, and no judgement left implicit: each angle carries the closed questions that decide whether its file is owed, and what was declined is reported.

The assumption it makes

Assumes specs live in the repo, next to the code they describe. Costs more judgement when writing than a template would — but the judgement is written down as questions, with the answer to take when unsure, so a small model and a careful human reach the same file set.

Its skills

• scrumia-feature
• scrumia-specs-find
• scrumia-specs-setup

Tags

• scrumia
• specs
• features
• tdd

What it plugs into

Install it

Read the source on GitHub