reversa-pricing-size

Compute risk-adjusted T-shirt sizing estimates from forward cycle artifacts.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-pricing-size-afsjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-pricing-size
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-pricing-size
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-pricing-size-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes ambiguity from feature scoping by deterministically measuring a feature's structural size from forward cycle artifacts, producing a T shirt sizing class with a risk adjustment.

Core Features & Use Cases

  • Deterministic feature sizing from requirements, doubts, plan depth, tasks, and touched principles.
  • Risk adjusted sizing that converts uncertainty into a final complexity class (S/M/L/XL/XXL).
  • Outputs for downstream pricing by generating _reversa_sdd/_pricing/<feature>/size.json and a human readable size.md.

Quick Start

Use the command /reversa-pricing-size after /reversa-to-do to calculate the active feature size and create size.json and size.md in the pricing output folder.

Frequently Asked Questions about reversa-pricing-size

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deterministically size a feature for pricing preparation?

To deterministically size a feature for pricing preparation, extract structural metrics from forward cycle artifacts and apply a risk adjusted formula. This process removes scoping ambiguity by measuring requirements, plan depth, tasks, and touched principles to generate a final T shirt complexity class.

What is risk adjusted T shirt sizing for feature complexity?

Risk adjusted T shirt sizing is a method that converts project uncertainty into a final complexity class ranging from S to XXL. It calculates structural size by analyzing forward cycle artifacts and applying a deterministic formula to account for doubts and requirements depth.

What inputs are needed to calculate feature size before pricing estimation?

Calculating feature size requires reading `.reversa/state.json` and loading sizing references for the formula and schema. The workflow needs forward cycle artifacts from requirements planning and task breakdown to extract metrics like plan depth and touched principles.

What files are generated when sizing a feature for downstream pricing?

Sizing a feature generates `size.json` compliant with v1.1 and a human readable `size.md` markdown report. These files are output to the `_reversa_sdd/_pricing/<feature>/` directory to provide structured data and reporting for downstream pricing estimation.

When should I run feature sizing in the development cycle?

Feature sizing should run after requirements planning and task breakdown, but before pricing estimation. It uses the `/reversa-pricing-size` command following `/reversa-to-do` to calculate the active feature size and create pricing outputs from the forward cycle artifacts.