reversa-pricing-size

Deterministic T-shirt sizing for features is calculated by reading forward-cycle artifacts like requirements and tasks, then applying a risk-adjusted mapping based on task counts and doubt severities to generate a consistent complexity class.

Standardize feature size estimation for pricing by transforming forward-cycle artifacts into deterministic structural metrics, outputting standardized size.json and size.md files according to a specific JSON schema to guide the next pricing step.

Risk adjustment for sizing software tasks works by incorporating task counts, doubt severities, plan depth, and principles touched into the structural size calculation to produce a risk-adjusted complexity class.

Yes, the heuristic applies total determinism by counting IDs, severities, and plan depth, tolerating custom templates and file variations across multiple agent runs while maintaining consistent feature sizing outputs.

You need forward-cycle artifacts such as requirements, doubts, plan, and tasks files to compute deterministic structural size metrics and generate the resulting size.json and size.md outputs for an active feature.

After computing deterministic feature metrics, the size.json and size.md files are generated and stored in the _reversa_sdd/_pricing/<feature>/ directory path according to the provided schema references.