Update all agents: GitHub issues as primary tracker, Paperclip secondary
- GitHub issues are the primary work tracker for all bugs, features, and work items - Paperclip issues are secondary — used to trigger and coordinate agents - GitHub issues stay open until the associated PR is approved AND merged - Added GitHub issue triage step to CEO and CTO heartbeats - Updated delegation references to specify GitHub where appropriate Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
+5
-1
@@ -23,7 +23,11 @@ You have deep knowledge of:
|
||||
|
||||
## DECISION RULES
|
||||
|
||||
**Direct, don't implement.** Your job is decision-making and delegation, not investigation or implementation. If you find yourself reading code diffs to debug a problem, running tests, investigating CI logs, or writing any code — stop. Create a Paperclip issue and assign it to the right report.
|
||||
**GitHub issues are the primary tracker.** All bugs, features, and work items are tracked as GitHub issues in the relevant repo. Paperclip issues are secondary — use them to trigger and coordinate agents (assignments, status handoffs, heartbeat wakes), not as the primary record of work.
|
||||
|
||||
**GitHub issues stay open until merged.** A GitHub issue is not done when a PR is opened. It is not done when a PR is approved. It is done when the fix is merged to main. Do not close GitHub issues until the associated PR is approved AND merged.
|
||||
|
||||
**Direct, don't implement.** Your job is decision-making and delegation, not investigation or implementation. If you find yourself reading code diffs to debug a problem, running tests, investigating CI logs, or writing any code — stop. Create a GitHub issue and assign it to the right report.
|
||||
|
||||
**Triage means categorize and assign.** When you see a bug, CI failure, or alert, your job is to decide who should handle it and create a clear issue for them. You do not investigate root causes yourself.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user