skills.rest
TencentBlueKing
TencentBlueKingOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tapd-story-specify

Generates technical clarification conclusions and spec.md specifications from requirement documents.

840|261|Updated Apr 18, 2019
Search Tags:#specification#spec generation#pipeline#tech-lead#tapd#requirement analysis#technical clarification
One-click install
npx skills add https://github.com/TencentBlueKing/bk-bcs --skill tapd-story-specify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tapd-story-specify
Source: https://github.com/TencentBlueKing/bk-bcs/tree/main/.agents/skills/tapd-story-pipeline/tapd-story-specify
Command: npx skills add https://github.com/TencentBlueKing/bk-bcs --skill tapd-story-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It bridges the gap between a finalized requirement document and development by running technical clarification and specification generation, ensuring requirements are technically feasible, unambiguous, and testable before coding starts.

Core Features & Use Cases

  • Two-stage execution: A tech-lead subagent first reviews the requirement and writes technical clarification conclusions into req.md, then generates a spec.md technical specification.
  • Question loop protocol: Unanswerable questions are appended to questions.md as open entries; the pipeline exits with blocked_on_questions and resumes after answers are provided.
  • Reentry and rollback support: Supports answer-based reentry, attempt-based rollback with iteration patches, round limits (3 for clarification, 5 for specify), and quality gate validation of spec.md against req.md.
  • Use Case: A TAPD story pipeline receives a new requirement; this skill clarifies technical feasibility, records open questions, and produces a validated spec.md with user scenarios, functional requirements, and success criteria.

Quick Start

Run the tapd-story-specify skill on the current requirement to perform technical clarification and generate the spec.md specification.

Frequently Asked Questions about tapd-story-specify

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

FAQPage Schema
How do I generate a technical specification from a requirement document?▼

Run this skill with req.md, context.md, and meta.yaml present in the working directory. A tech-lead subagent first writes technical clarification conclusions into req.md, then generates spec.md, which is validated against a quality gate before the phase advances to tech-clarified.

What happens when the skill cannot answer a clarification question?▼

Unanswerable questions are appended to questions.md as open entries and the pipeline exits with blocked_on_questions. After the caller marks entries as answered, re-invoking with action=answer resumes execution from the correct stage.

How many question rounds are allowed during clarification and specification?▼

The technical clarification stage allows up to 3 question rounds per attempt, and the specify stage allows up to 5 rounds with its counter reset after clarification completes. Exceeding the limit escalates to a rollback reentry.

Can the specification stage be re-run if spec.md is insufficient?▼

Yes. A later stage can return spec_insufficient, the caller resets the phase to initialized and writes an iteration patch file, and the skill re-executes with an incremented attempt counter while preserving previous artifacts.

When is technical clarification skipped for a requirement?▼

Clarification is skipped for trivial requirements such as configuration changes, copy edits, or simple bug fixes with no technical risk. The subagent records a dropped entry and marks the requirement as technically approved.

Related Skills

Explore More Software Engineering Skills→
I-SynergyI-Synergy

user-story

Draft user stories with Gherkin acceptance criteria for bounded contexts.

Official
Advanced
Oruga420Oruga420

ralphinho-rfc-pipeline

Decompose oversized features into verifiable work units via an RFC-driven pipeline.

Community
Advanced
Rinzler78Rinzler78
1

bmad-sprint-planning

Generate sprint-status.yaml from epic documents and story inventories.

Community
Advanced
easingthemeseasingthemes
6

dx-req-import

Validate requirements documents and generate formal spec structures.

Community
Intermediate