reversa-pricing-size

T-shirt sizing for software features works by reading forward-cycle artifacts like requirements, doubts, and plan depth to compute a deterministic size class (S/M/L/XL/XXL) using a documented formula with risk adjustment. This approach reduces planning uncertainty by analyzing high-severity doubts and task breadth.

To estimate feature complexity from generated task lists, run the sizing command after your to-do tasks are created. It reads your feature folder artifacts and applies schema validation to generate a size.json output, applying atomic updates with optional recalculation guardrails to ensure accurate structural metrics.

Yes, structural sizing applies to features stored in the forward-cycle folder structure. It requires resolving the output and forward folders from a state.json configuration file and reads artifacts from the active feature folder to generate pricing metrics.

The best way to compute deterministic T-shirt sizes for software rebuilds is using a versioned sizing formula that reads requirements and plan depth. This method generates risk-aware notes summarizing high-severity doubts and plan breadth, providing structured outputs for the pricing pipeline.

Yes, you need to generate to-do tasks and resolve forward-cycle artifacts before sizing a feature. The sizing process reads these artifacts, including resolved doubts and plan depth, to accurately apply the risk-adjusted complexity formula and generate the final size classification.