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.