What problem does it solve?
Product teams often receive vague, incomplete TAPD requirements that lead to rework and misaligned implementation. This Skill extracts stories in the "planning" (backlog) state from TAPD, runs a structured multi-dimensional clarification dialogue, and produces a standardized requirement document that is written back to TAPD.
Core Features & Use Cases
- Structured Clarification: Applies 5W1H questioning, Example Mapping, and BDD acceptance criteria (Given-When-Then) to turn ambiguous stories into testable requirements, with a two-round Framing/Detailing mode for complex stories.
- Standardized Document Generation: Produces a Markdown requirement document from a fixed template (background, functional/non-functional requirements, business rules, acceptance criteria, scope, assumptions) and saves it to
docs/reqs/ with a concise 4-10 character filename.
- DoR Quality Gate & TAPD Write-back: Runs an 8-item Definition of Ready checklist before writing back; only fully passing stories are advanced to
approved, otherwise the description is updated while status stays backlog.
- Use Case: A product manager asks to clarify three TAPD story IDs; the Skill fetches each story, asks batched blocking/non-blocking questions, generates the documents, and returns a summary table with DoR results and file paths.
Quick Start
Ask the assistant to clarify TAPD story 1001234 in workspace 20000001 and write the standardized requirement document back to TAPD.
