tapd-story-score

Estimates effort, Fibonacci size, and RICE business value for TAPD requirement documents.

840|261|Updated Apr 18, 2019
One-click install
npx skills add https://github.com/TencentBlueKing/bk-bcs --skill tapd-story-score
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tapd-story-score
Source: https://github.com/TencentBlueKing/bk-bcs/tree/main/.agents/skills/tapd-story-evaluation/tapd-story-score
Command: npx skills add https://github.com/TencentBlueKing/bk-bcs --skill tapd-story-score

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually estimating effort, sizing, and business value for TAPD requirements is inconsistent and time-consuming. This Skill applies standardized PERT three-point estimation, Fibonacci size scoring, and RICE prioritization to produce objective, traceable scores written back into the requirement document and TAPD fields.

Core Features & Use Cases

  • PERT Effort Estimation: Computes optimistic, most-likely, and pessimistic hours using type-specific baselines (development, operations, documentation) and adjustment factors, rounded to 0.5h.
  • Fibonacci Size Scoring: Scores five dimensions (scope, complexity, dependencies, risk, verification cost) and maps them via maxDim anchoring and avgDim calibration to a Fibonacci size written to the TAPD size field.
  • RICE Business Value: Calculates Reach, Impact, Confidence, and Effort into a RICE score written to the TAPD business_value field, fully decoupled from size.
  • Use Case: A product manager receives a new TAPD story and asks the agent to score it; the Skill checks for existing complete scores, runs a full estimation round if needed, updates the requirement document, and outputs structured results for the parent skill to sync back to TAPD.

Quick Start

Score this TAPD requirement document for effort, size, and RICE business value using the standard baselines.

Frequently Asked Questions about tapd-story-score

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

FAQPage Schema
How do I estimate effort for a TAPD user story?

Use PERT three-point estimation: determine optimistic, most-likely, and pessimistic hours from type-specific baselines, then compute E = (O + 4M + P) / 6 rounded to 0.5h. The Skill applies adjustment factors like technical difficulty or cross-team dependencies to the baseline M value.

How is Fibonacci story size calculated from scoring dimensions?

Score five dimensions (scope, technical complexity, dependencies, risk, verification cost) from 1 to 5, then map maxDim and avgDim to a Fibonacci number using anchor-and-calibrate mapping. Sizes of 8 suggest splitting the story, and 13 or above requires splitting.

What is the RICE score formula for requirement prioritization?

RICE Score = (Reach × Impact × Confidence) / Effort. Reach is the percentage of affected users, Impact ranges from 1 to 10 by priority, Confidence is 25-100% based on requirement clarity, and Effort is estimated hours divided by 8 to get person-days.

Does the skill re-score requirements that already have estimates?

No, if effort, size, and RICE scores are complete with traceable reasoning and the user has not requested re-evaluation, the Skill exits without re-scoring. If any scoring artifact is incomplete, it runs a full new round rather than patching individual fields.

Can the skill handle operations and documentation tasks, not just development stories?

Yes, it supports three requirement types: development, operations, and documentation. Each type has its own effort baseline table with low, medium, and high complexity O/M/P values defined in the effort baseline reference.