tapd-story-review

Orchestrates TAPD requirement review rounds, comment processing, and approval status transitions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After requirement clarification or story-splitting results are written back to TAPD, teams still need a repeatable way to request reviews, collect reviewer comments, and decide whether a requirement is approved or needs rework. This Skill automates that review loop so no feedback is lost and status transitions stay consistent.

Core Features & Use Cases

  • Request Review: Transitions the parent story to for approve, posts a structured review-initiation comment mentioning reviewers, and records local review metadata per round.
  • Process Feedback: Pulls new parent and child story comments, classifies them into accept / reject / needs-user-confirmation, and outputs a verdict of waiting_review, needs_rework, approved, or blocked.
  • Check Status: Reads the parent story status without modifying anything, reporting whether the review is approved, in progress, or abnormal.
  • Use Case: After splitting a requirement into child stories in TAPD, ask the Skill to request an evaluation review from @alice and @bob, then later process their comments and automatically advance the parent story to approved once any reviewer approves.

Quick Start

Ask the assistant to start a clarification review for TAPD requirement 12345 with reviewers @alice and @bob.

Frequently Asked Questions about tapd-story-review

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

FAQPage Schema
How do I request a TAPD requirement review with specific reviewers?

Provide the parent requirement ID and a reviewer list such as @alice @bob. The Skill transitions the story to for approve, posts a structured review-initiation comment mentioning the reviewers, and records the round in local metadata.

How does the Skill process reviewer comments on TAPD stories?

It pulls new comments from the parent story and, for evaluation phases, child stories, then classifies each as accept, reject, or needs-user-confirmation. It outputs a verdict of waiting_review, needs_rework, approved, or blocked with a structured feedback list.

What is required before starting a TAPD story review?

The TAPD MCP service must be available, the parent requirement description must already be written back, and a workspace ID must come from user input or project.json. First-round reviews also require an explicit reviewer list.

When does the Skill mark a TAPD requirement as approved?

Under the default any_one_reviewer_approve rule, a single reviewer comment with conclusion approve and blocking set to no triggers approval. The Skill then restores the original owner and transitions the parent story to approved.

Can the Skill review child stories along with the parent requirement?

Yes, when include_children is true, which is the default for the evaluation phase. It automatically reads the parent story's children_id list, queries each child story, and includes their comments in the feedback summary.

What happens when reviewer feedback requires business decisions?

Comments involving business trade-offs are marked needs-user-confirmation and the Skill returns a blocked verdict with a structured question list. Once answers are passed back via answered_questions, processing resumes.