tapd-product-discovery

Start the product discovery flow by providing the idea source and your TAPD workspace_id. The Skill creates or locates a product parent story in backlog state, then guides research, PRD drafting, and prototype review before any engineering tickets exist.

After the parent story reaches approved state, the Skill evaluates whether each role is actually needed based on interaction, page, and API/data criteria. It creates only the necessary child stories under the parent and records skip reasons for the rest.

Use product discovery when no complete PRD exists yet, such as raw ideas, research needs, or prototype review. If the PRD, design, and API docs are already confirmed, hand the work to tapd-story-pipeline for engineering implementation instead.

Yes. Pure backend tasks, configuration changes, script jobs, and text-only edits can skip the prototype Spec and BKUI HTML prototype. The Skill records the skip reason in the TAPD parent story before continuing to product review.

The Skill stops all TAPD write operations and instead outputs the local product documents plus the manual ticket creation fields. No stories_create or stories_update calls are made without MCP availability and explicit user confirmation.

The parent story moves through backlog, doing, for approve, approved, and done. The done state only means product-side work is complete; release status continues to be tracked by the frontend and backend child stories.