bk-monitor-tapd-dev

TAPD Ticket Development Assistant

Workflow

Step 1: Get the TAPD ID and verify the branch (blocking)

1. Get the ID: provided by the user or extracted from the branch name (git branch --show-current, match #(\d+)）
2. Verify whether the branch contains this ID
   • Match → continue
   • No match → ask the user to choose (create branch/continue development)

Step 2-3: Get the ticket

1. Parse workspace_id = id.substring(2, 10)
2. Call MCP (stories_get, bugs_get, tasks_get) to get ticket details and comments

Step 4-6: Analysis and development

1. Analyze the requirement (title, description, comments, due date)
2. Generate a plan according to dev-plan-template.md
3. Wait for user confirmation before starting development

Notes

• Branch verification is the first priority
• The plan requires user confirmation before development can begin
• When comments conflict with the description, the latest comment takes precedence

---

📦 Available resources

• skill://bk-monitor-tapd-dev/references/branch-workflow.md
• skill://bk-monitor-tapd-dev/references/dev-plan-template.md
• skill://bk-monitor-tapd-dev/references/mcp-calls.md
• skill://bk-monitor-tapd-dev/references/tapd-mcp-guide.md

---

📦 Available resources

• skill://bk-monitor-tapd-dev/references/branch-workflow.md
• skill://bk-monitor-tapd-dev/references/dev-plan-template.md
• skill://bk-monitor-tapd-dev/references/mcp-calls.md
• skill://bk-monitor-tapd-dev/references/tapd-mcp-guide.md

Determine whether loading is needed according to the IF-THEN rules in SKILL.md