tapd-story-tasks

Generates and validates implementation task lists from plan and research documents via subagents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning a feature plan into an executable, well-structured task list is error-prone: tasks may miss dependencies, lack test coverage, or fail to map back to the plan. This Skill automates the tasks phase of an iterative story pipeline by generating a full tasks.md from plan.md and research.md, then independently validating it for compliance.

Core Features & Use Cases

  • Two-stage subagent execution: Renders two isolated subagent prompts—one calling speckit-tasks to generate tasks.md, another calling speckit-analyze to produce a compliance report (tasks-report.md).
  • Content gating and verdict routing: Checks task format, user-story slicing, TDD coverage, dependency ordering, and plan completeness; routes pass / needs_fix / plan_insufficient / spec_insufficient verdicts to retry or rollback workflows.
  • Reentrant retry protocol: Supports up to 3 rounds per attempt and rollback re-entry to plan or specify phases, with meta.yaml state tracking and append-only process.log.
  • Use Case: During a TAPD story pipeline, after the plan phase completes, invoke this Skill to produce a validated tasks.md where every user story has independently testable, dependency-ordered tasks before implementation begins.

Quick Start

Run the tasks phase for the current story to generate tasks.md from plan.md and research.md, then validate it with the analyze report.

Frequently Asked Questions about tapd-story-tasks

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

FAQPage Schema
How do I generate a tasks.md file from a feature plan?

Provide plan.md and research.md in the working directory, then run the tasks phase. It renders a subagent prompt that calls speckit-tasks to produce tasks.md with checkbox-formatted, dependency-ordered tasks.

How is the generated task list validated for quality?

A second subagent runs speckit-analyze to produce tasks-report.md, checking task format, user-story slicing, TDD coverage, dependency ordering, walking-skeleton completeness, and mapping back to plan.md requirements.

What happens when the tasks compliance check fails?

A needs_fix verdict retries generation and analysis within the same attempt, up to 3 rounds. plan_insufficient or spec_insufficient verdicts trigger rollback re-entry to the plan or specify phase with a documented root cause.

What are the prerequisites for running the tasks phase?

The story phase must be 'researched', and plan.md, research.md, and optionally data-model.md must exist in the working directory. The pipeline orchestrator must also have rewritten context.md for the current stage.

Why are task generation and analysis split into two subagents?

speckit-analyze is an independent skill that must run after tasks.md is written to disk, so a fresh agent process is launched for the analysis stage. This isolation keeps generation and validation concerns separate.