tapd-story-breakdown

Breaks down large TAPD requirements into scoped sub-requirement documents with traceability validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Large product requirements in TAPD are often too big to deliver and test in one iteration. This Skill decomposes oversized requirements into small, well-scoped sub-requirements with controlled workload size, so development stays predictable and each deliverable is easy to verify.

Core Features & Use Cases

  • Split Decision Matrix: Combines user story counting with a five-dimension qualitative size assessment to decide whether to split, merge, or skip.
  • Contract-First Dependency Management: Detects strong cross-requirement dependency chains and extracts an interface-contract sub-requirement as a Wave 1 baseline so remaining items can proceed in parallel waves.
  • Traceability Gate: Builds an element-centric traceability matrix (targeting 95%+ coverage) and runs six consistency checks, with a patch-then-resplit recovery loop before handing unresolved gaps to the user.
  • Use Case: A product manager submits a 40-person-hour TAPD story; the Skill splits it into sub-requirement documents saved under docs/reqs/<parent-name>/, each with at most two user stories, Given-When-Then acceptance criteria, and a wave-based delivery plan.

Quick Start

Ask the agent to break down TAPD story 10123456 in workspace 5678 into sub-requirements and save the resulting documents under docs/reqs.

Frequently Asked Questions about tapd-story-breakdown

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

FAQPage Schema
How do I split a large TAPD requirement into sub-requirements?

Provide the requirement ID and workspace ID; the Skill counts user stories, runs a five-dimension size assessment, and applies a decision matrix to split by function module, business process, or technical layer. Each sub-requirement gets a specification document saved under docs/reqs/<parent-name>/.

When should a requirement not be split?

Requirements with two or fewer user stories and low-to-medium assessed size are left unsplit. Tiny fragmented stories totaling under eight person-hours are merged into one or two cohesive sub-requirements instead of being split further.

Does this Skill work standalone or only with tapd-story-evaluation?

It is designed as a sub-skill invoked by tapd-story-evaluation and does not trigger independently. The parent skill calls it repeatedly whenever a scored sub-requirement exceeds the 24 person-hour ceiling, applying identical split logic each time.

How are dependencies between sub-requirements handled?

Dependencies are classified as strong, weak, or optional. When strong cross-requirement chains exist, an interface-contract sub-requirement is extracted as Wave 1, downgrading other items to weak contract dependencies so they can be developed in parallel in later waves.

What happens if the traceability check fails after splitting?

The Skill follows a patch-then-resplit strategy with a budget of two retries: first a targeted patch or full resplit based on failure classification, then a complete re-split. If checks still fail, it outputs the gap details and flags them for manual handling without blocking the workflow.