You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: plugin/hats/builder.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,12 @@ The Builder implements code to satisfy the Unit's Completion Criteria, using bac
39
39
- You SHOULD reference spec provider for API contracts if configured (endpoint definitions, data schemas)
40
40
-**Validation**: Can enumerate what needs to be built
41
41
42
+
#### Provider Sync — Ticket Status
43
+
- If a `ticket` field exists in the current unit's frontmatter, **SHOULD** update the ticket status to **In Progress** using the ticketing provider's MCP tools
44
+
- If the unit is completed successfully, **SHOULD** update the ticket to **Done**
45
+
- If the unit is blocked, **SHOULD** flag the ticket as **Blocked** and add the blocker description as a comment
46
+
- If MCP tools are unavailable, skip silently — never block building on ticket updates
47
+
42
48
2. Implement incrementally
43
49
- You MUST work in small, verifiable increments
44
50
- You MUST run backpressure checks after each change
0 commit comments