reversa-pricing-size

Computes deterministic size metrics and generates size.json and size.md.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-pricing-size-stribus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-pricing-size
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-pricing-size
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-pricing-size-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Dimensiona de forma determinística o tamanho estrutural da feature ativa lendo artefatos do ciclo forward da REVERSA e produz size.json e size.md, fornecendo métricas claras para o planejamento.

Core Features & Use Cases

  • Lê artefatos do ciclo forward (requirements, doubts, plan, tasks) para calcular o tamanho da feature.
  • Gera size.json (schema v1.1) e size.md com notas, classe de complexidade e score auxiliar.
  • Suporta o fluxo entre etapas (/reversa-to-do, /reversa-pricing-estimate) para planejamento e orçamento.

Quick Start

Diga ao sistema para dimensionar a feature atual usando o fluxo determinístico de sizing.

Frequently Asked Questions about reversa-pricing-size

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

FAQPage Schema
How do I compute deterministic feature sizing metrics for software planning?

To compute deterministic feature sizing, read forward cycle artifacts including requirements, doubts, plan, and tasks to generate size.json and size.md files with complexity classes and auxiliary scores for planning.

What is the correct workflow order for generating size.json and size.md in REVERSA?

Generate size.json and size.md within the REVERSA forward cycle by running the sizing step after /reversa-to-do and before /reversa-pricing-estimate, reading existing state from the .reversa directory to analyze tasks.

When do I need to generate a size.json file with complexity classes for feature planning?

Generate a size.json file when you need deterministic and auditable structural size metrics for feature planning, producing schema v1.1 outputs that include notes, complexity classes, and auxiliary scores.

Does deterministic feature sizing require specific input artifacts to analyze requirements and doubts?

Yes, deterministic feature sizing requires reading forward cycle artifacts including requirements, doubts, plan, and tasks from the .reversa directory to accurately calculate the structural size of the active feature.

Can I use deterministic sizing outputs directly for project budget estimation?

Deterministic sizing outputs like size.json and size.md provide structural size metrics and complexity classes, but they feed directly into the subsequent /reversa-pricing-estimate step to calculate the final project budget.

Why does feature sizing output both size.json and size.md files to the _reversa_sdd directory?

Feature sizing outputs both size.json and size.md to the _reversa_sdd directory to deliver a machine-readable schema v1.1 JSON and a human-readable markdown summary, ensuring a deterministic and auditable process.