skills.rest
diegouis
diegouisCOMMUNITY
Explore all skills by this author →
GitHub

rom-estimate

Generate ROM effort estimates from project documents into CSV files.

Updated Aug 27, 2026
Search Tags:#planning#project management#scoping#estimation#effort estimation#rom
One-click install
npx skills add https://github.com/diegouis/provectus-marketplace --skill rom-estimate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rom-estimate
Source: https://github.com/diegouis/provectus-marketplace/tree/main/plugins/proagent-delivery/skills/rom-estimate
Command: npx skills add https://github.com/diegouis/provectus-marketplace --skill rom-estimate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Rough Order of Magnitude (ROM) effort estimates for projects, transforming raw project documents into structured, actionable data.

Core Features & Use Cases

  • Automated Scope Analysis: Parses project documents (roadmaps, PRDs, task lists) to identify epics and features.
  • Effort Estimation: Assigns effort levels (XS, S, M, L, XL) and duration ranges to each feature.
  • Use Case: You have a new product roadmap document. Use this Skill to break down the roadmap into features, estimate the effort for each, and generate a CSV report detailing the project's scope and resource requirements.

Quick Start

Use the rom-estimate skill to analyze the project scope described in the file '/path/to/project/scope.md'.

Frequently Asked Questions about rom-estimate

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

FAQPage Schema
How do I generate a Rough Order of Magnitude effort estimate from project documents?▼

Yes, you can estimate project effort from Google Drive documents, local files, or inline text input. The Skill analyzes the provided scope, breaks down tasks into features, and generates effort estimates with a CSV report detailing resource requirements.

How does automated scoping break down a roadmap into development effort levels?▼

Automated scoping works by parsing project documents to identify epics and features. It then assigns effort levels from XS to XL and duration ranges to each feature, transforming raw project lists into structured, actionable effort estimates.

What is the best way to convert a product requirements document into an effort estimation CSV?▼

The best way to convert a PRD into an estimation CSV is using an automated ROM estimator. It analyzes the document's scope, estimates effort levels and durations for each feature, and exports the structured data as a semicolon-delimited CSV file.

Can I use inline text input for project scoping instead of uploading a file?▼

Yes, inline text input is supported for project scoping alongside local files and Google Drive integration. You can provide task lists or project descriptions directly as text to generate effort estimates and summary analysis.

What formats and data structures are output by ROM effort estimation tools?▼

ROM effort estimation tools output a semicolon-delimited CSV file containing the parsed features and their assigned effort levels. They also generate a summary analysis detailing the project's scope and resource requirements.

Related Skills

Explore More Product & Management Skills→
OvidOvid
92

alignment

Compare intent and action documents to surface requirement gaps and scope creep.

Community
Intermediate
timfogarty1549timfogarty1549

musmem-extract-distinct-athletes

Extract athlete names from MusMem semicolon-delimited files into candidate-group TSVs.

Community
Intermediate
zhayujiezhayujie
46.4k

web-fetch

Fetch web page HTML and extract title and readable text.

Community
Basic
dralgorhythmdralgorhythm
111

estimating-work

Estimate development effort using story points and T-shirt sizing.

Community
Intermediate