TAPD Requirement Task Analysis

Usage Scenarios

• Users request to analyze task scheduling for a specific requirement
• Users want to determine if the requirement progress is normal
• Users hope to identify delay risks, responsible person distribution, or testing gaps from the task perspective

Execution Steps

1. First confirm the analysis target:
   • If the user directly provides a

     story_id

     , use it directly
   • If the user provides a local Markdown file, first read the

     tapd_id

     from the frontmatter
2. Execute:

tapd story get <story-id>
tapd story tasks <story-id> --all

1. Read:

   • references/analysis-output.md

2. Output in accordance with specifications:
   • Analysis target
   • Overview
   • Key summary
   • Risks and issues
   • Recommended actions
   • Details

Analysis Focus

• Whether there are too few in-progress tasks, leading to slow overall progress
• Whether a large number of unstarted tasks are piled up in the later scheduling period
• Whether testing tasks are significantly later than development tasks
• Whether there is a situation where responsible persons are overly concentrated or no one is in charge
• Whether man-hours, time windows, and task status match

Notes

• Do not directly copy the original command output
• Details are grouped by

  In Progress / Not Started / Completed

  by default
• If there are a large number of tasks, only keep key tasks and abnormal tasks