pricing

Estimates software feature costs in hours, work days, and ILS using PERT and Function Points.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/levori119/skyboard --skill pricing-levori119
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pricing
Source: https://github.com/levori119/skyboard/tree/main/.claude/skills/pricing
Command: npx skills add https://github.com/levori119/skyboard --skill pricing-levori119

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Producing a defensible cost estimate for a software feature or MVP is hard: gut-feel numbers fail external review, and mixing hourly and daily rates creates confusion. This Skill generates auditable price quotes with ranges, dual pricing bases, and documented methodology. ## Core Features & Use Cases - Dual pricing bases: Every estimate shows both net-hours basis (lower bound, pay-per-hour) and work-day basis (market rate, ~x1.5), with 1 work day = 4-5 effective hours. - Rigorous estimation methods: Quick bottom-up rules of thumb for common work types, plus three converging methods for formal documents - WBS with three-point PERT, IFPUG Function Points, and measuring existing code LOC. - Timeline and export: Converts net hours to realistic programmer-months (hours / 108, not 160) and exports formatted RTL HTML quotes based on the MVP_PRICING.html template. - Use Case: A stakeholder asks for an MVP price quote. The Skill defines the baseline scope, applies per-feature hour rules, adds 15% QA and infrastructure lines, and outputs a range in ILS before VAT with both pricing bases and cited rate sources. ## Quick Start Ask the assistant to estimate the cost and timeline for a new feature or MVP, describing the scope, existing infrastructure, and any exclusions.

Frequently Asked Questions about pricing

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

FAQPage Schema
How do I estimate the cost of a software feature or MVP?

Define a written baseline of scope, assumptions, and exclusions first, then break each feature into sub-tasks and price them with rules of thumb in net hours. Add a cross-cutting infrastructure line and 15% for integration QA, then present a range rather than a single number.

What is the difference between hourly basis and work-day basis pricing?

Hourly basis uses net hours multiplied by an hourly rate and suits pay-per-reported-hour arrangements. Work-day basis converts hours at 4-5 effective hours per day and reflects how the market actually prices, roughly 1.5 times the hourly basis.

How do I make a cost estimate defensible under external review?

Use three independent methods that must converge: WBS with three-point PERT estimation, IFPUG Function Points counting, and measuring lines of code of similar existing features. If the methods diverge, investigate before publishing the estimate.

How do I convert estimated hours into a project timeline?

Divide net hours by 108 to get programmer-months, based on 5 effective hours per day across 21.7 work days. Dividing by 160 hours per month produces an overly optimistic schedule and should be avoided.

What are the limitations of rule-of-thumb hour estimates?

Rule-of-thumb hours are engineering estimates, not sourced data, and must be labeled as such. Rates should be verified online at each use, and estimates that deviate by an order of magnitude from calibrated anchors should be rechecked.