Overview
Handle requirement work before the PRD: idea recording, requirement source organization, user research, competitive analysis, business analysis, PRD, page prototype Spec, BKUI HTML prototype, prototype review, and product review. The process starts from the product parent ticket and proceeds as "idea recording -> product research -> PRD -> page prototype Spec -> BKUI HTML prototype -> prototype review -> product review -> role ticket splitting"; after the product plan is approved, create design, frontend, and backend sub-tickets as actually needed.
After the frontend and backend sub-tickets are created, continue using the existing R&D process; it does not replace tapd-story-clarification、tapd-story-evaluation、tapd-story-pipeline。
Applicable scenarios
- The user only has an idea, boss requirement, user feedback, competitive observation, or business problem, and does not yet have a complete PRD.
- The user wants to do user research, competitive analysis, business analysis, or prototyping first, and then organize it into a PRD.
- The PRD is ready, and a page prototype Spec and BKUI HTML prototype need to be generated for product, design, and frontend review.
- A product plan has passed review, and TAPD sub-tickets need to be split by design, frontend, and backend.
- Need to explain which TAPD statuses product, design, frontend, and backend each use.
Not applicable scenarios
- The PRD, design mockups, and interface documents are all confirmed, and only R&D implementation is needed: use
tapd-story-pipeline。 - There is already a standardized requirements document, and only clarification or supplementary acceptance criteria are needed: use
tapd-story-clarification。 - There is already a parent requirement, and it needs to be split and scored by user story: use
tapd-story-evaluation。 - Only handle code, build, release, or Code Review: use the corresponding R&D Skill.
Prerequisites
- The TAPD MCP service is available.
- The user provides workspace_id, or the project root directory
project.jsoncontainsworkspace_id。 - Before creating or updating a TAPD ticket, first show the planned changes to the user, and call MCP only after confirmation.
Input
| Parameter | Source | Required | Description |
|---|---|---|---|
| Requirement source | User input / TAPD parent ticket | Yes | Ideas, boss requirements, user feedback, competitive observations, existing drafts, etc. |
| Product parent ticket ID | User input / create new | No | Reuse if a parent ticket already exists; otherwise create one |
| workspace_id | User input > project.json | Yes | TAPD workspace ID |
| owner | User input > project.json | No | Product owner or current assignee |
| Background knowledge | User-specified > AGENTS.md automatic lookup | No | Business description, user materials, competitive materials, architecture constraints, frontend and backend specifications, etc. |
Status flow
Product parent ticket
backlog -> doing -> for approve -> approved -> done
| Status | Meaning |
|---|---|
backlog |
The requirement source has entered TAPD, but product research has not yet started |
doing |
Research, analysis, prototyping, or PRD is in progress |
for approve |
The PRD or product plan is awaiting review |
approved |
Product solution approved; role sub-tasks can be split |
done |
Product-side delivery completed; role sub-tasks have been created or confirmed as not needed |
Design sub-task
backlog -> todo(已规划) -> designing -> design approved -> done
| Status | Meaning |
|---|---|
backlog |
Design sub-task created, awaiting scheduling |
todo(已规划) |
Design owner, scope, and schedule confirmed |
designing |
Designer is producing interaction, visual, prototype, or design specification |
design approved |
Design deliverables have passed review and are available for R&D use |
done |
Design materials have been delivered and archived |
Frontend and backend sub-tasks
backlog -> for approve -> approved -> todo(已规划) -> doing -> for test -> tested -> for gray -> grayed -> done
Frontend and backend sub-tasks only record their respective R&D progress, and no longer include product research and PRD review content.
Execution process
1. Determine the current entry point
First determine which stage the user is in:
| User input | Handling method |
|---|---|
| Only an idea or requirement source | Create or locate the product parent task, enter product pre-work |
| Currently doing research / competitors / PRD | Reuse the product parent task, advance to doing |
| PRD awaiting review | Write back the product document, advance to for approve |
| Product solution approved | Advance to approved, enter role task splitting |
| Only R&D implementation is required | Do not use this process; prompt to use the existing R&D process |
2. Prepare the product parent task
2.1 Determine workspace_id and owner
Priority:
- Explicitly provided by the user
project.json- Ask the user
2.2 Existing product parent task
When the user provides the product parent task ID, call TAPD MCP stories_get to read the task:
workspace_id: <workspace_id>
id: <产品父单 ID>
with_v_status: "1"
After reading, check:
- Whether the task exists
- Whether it is a parent task or can serve as one
- Whether the current status is suitable for further progress
2.3 No product parent task
If there is no parent task, first organize the creation plan and ask the user to confirm. After confirmation, call stories_create:
workspace_id: <workspace_id>
name: <需求名称>
description: <产品父单初始描述>
with_v_status: "1"
v_status: "backlog"
owner: <owner>
creator: <owner>
priority_label: <High|Middle|Low>
created: <当前时间>
The initial description of the parent task uses references/product-requirement-template.md。
3. Product research and PRD
Before execution, read references/product-discovery-guide.md, and choose the content to supplement according to requirement complexity:
- Requirement source and triggering background
- Target users and usage scenarios
- Current problems and business impact
- User research conclusions
- Competitor or alternative solution analysis
- In-project constraints
- Product goals and measurement metrics
- Prototype, flow, or interaction sketch
- PRD scope, acceptance criteria, and non-goals
If the user has not yet started research, first output a research outline and advance the product parent task to doing. If the user has already provided research materials, directly organize them into a product document.
Save the product document to:
docs/reqs/product/<产品父单短标题>.md
Extract the file name from the requirement name, keeping 4-12 Chinese characters; if there is a duplicate name, append the short requirement ID.
4. Page prototype Spec and HTML prototype
After the PRD is completed, first determine whether a page prototype is needed.
Scenarios requiring a page prototype:
- Adding or adjusting pages, tables, forms, modals, drawers, or charts
- Product, design, and frontend need to confirm the page structure before task splitting
- The PRD already contains multiple pages or complex interactions
Scenarios that can be skipped:
- Pure backend capability
- Pure configuration or script tasks
- Only copy changes and does not affect page structure
- Existing reusable design mockup or prototype link
Read when needed references/prototype-spec-template.md, generate the page prototype Spec, and save it to:
docs/reqs/product/<产品父单短标题>.prototype.md
After the user confirms the page prototype Spec, read references/bkui-html-prototype-guide.md, generate the BKUI HTML prototype, and save it to:
docs/reqs/product/prototypes/<产品父单短标题>-preview.html
After the prototype review passes, proceed to the product review and role ticket splitting. If the page prototype is skipped, record the reason in the product parent ticket.
5. Product review
When the PRD is ready and the prototype is complete or the reason for skipping has been recorded:
- Show the user the product document path and status changes that will be written back.
- After the user confirms, read the local product document content and call
stories_updateto write back to the product parent ticketdescription。 - Advance the product parent ticket status to
for approve。
After the review passes, the user can directly say "product review passed" or provide the review conclusion. After confirmation, advance the product parent ticket to approved。
6. Role ticket splitting
After the product parent ticket is approved , read references/role-ticket-splitting.md, and determine which child tickets are needed.
| Child ticket | Creation condition |
|---|---|
| Design child ticket | Requires interaction flow, visual mockups, prototype refinement, information architecture, or design review |
| Frontend child ticket | Requires pages, components, interactions, forms, frontend state, frontend integration, or tracking |
| Backend child ticket | Requires APIs, data models, permissions, state machines, background tasks, messages, or external system integration |
Simple requirements can skip some roles. The reason for each skipped item must be stated in the product parent ticket.
Child ticket creation fields
Before calling stories_create , first show the child ticket plan and ask the user to confirm. After confirmation, create them one by one:
workspace_id: <workspace_id>
name: <角色前缀 + 子单名称>
parent_id: <产品父单 19 位 ID>
description: <角色子单说明>
with_v_status: "1"
v_status: "backlog"
owner: <对应负责人,未知则使用 owner 并标注待分配>
creator: <owner>
priority_label: <继承产品父单或用户指定>
created: <当前时间>
Suggested role prefix:
[设计] <需求名称>[前端] <需求名称>[后端] <需求名称>
7. Write back to the parent ticket and end the product-side process
After the child tickets are created, update the product parent ticket description and add:
- Child ticket list and links
- Reasons why role child tickets were not created
- Suggested next steps for the R&D side
After the user confirms, advance the product parent ticket to done。
Product parent ticket done does not mean the feature is live; it only means the product-side work is complete. The launch status continues to be recorded by the frontend/backend child tickets.
8. Output summary
Output format:
## 产品前置流程完成
| 项目 | 结果 |
|------|------|
| 产品父单 | #xxx,done |
| 产品文档 | docs/reqs/product/xxx.md |
| 页面原型 Spec | docs/reqs/product/xxx.prototype.md / 未生成:原因 |
| HTML 原型 | docs/reqs/product/prototypes/xxx-preview.html / 未生成:原因 |
| 设计子单 | #xxx / 未创建:原因 |
| 前端子单 | #xxx / 未创建:原因 |
| 后端子单 | #xxx / 未创建:原因 |
| 下一步 | 设计进入设计流程;前端/后端进入澄清、评估、规划、实现流程 |
Relationship with existing Skills
| Stage | Skill used |
|---|---|
| Ideas, research, PRD, product review | tapd-product-discovery |
| Frontend/backend child ticket requirement clarification | tapd-story-clarification |
| Frontend/backend child ticket splitting, scoring | tapd-story-evaluation |
| Iteration planning | tapd-iteration-plan |
| Single requirement R&D implementation | tapd-story-pipeline |
| Iteration R&D execution | tapd-iteration-runner |
Error handling
| Scenario | Handling |
|---|---|
| TAPD MCP unavailable | Stop TAPD writes, output local documents and manual ticket creation fields |
| Missing workspace_id | First read from project.json ; if still missing, ask the user |
| Product parent ticket does not exist | Prompt the user to reconfirm the ID, or create a new parent ticket |
| User has not confirmed the status change | Do not call stories_create / stories_update |
| Sub-task creation failed | Retry once; if it still fails, output the manual creation fields |
| Unable to determine whether a certain role is needed | Mark as pending confirmation; do not automatically create the sub-task for this role |
Reference file
| File | Purpose |
|---|---|
references/product-discovery-guide.md |
Product research, analysis, and PRD organization guide |
references/product-requirement-template.md |
Product parent task description template |
references/prototype-spec-template.md |
Page prototype Spec template |
references/bkui-html-prototype-guide.md |
BKUI HTML prototype generation specification |
references/role-ticket-splitting.md |
Design, frontend, and backend sub-task splitting rules |