cartsnitch/.github
12
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: sync company/ export snapshot with current configuration

Browse Source 
- Removes rollback-rhonda (decommissioned agent)
- Adds deal-dottie agent files (AGENTS.md, mcp.json)
- Updates .paperclip.yaml: removes rollback-rhonda, adds deal-dottie
- Updates skills directory to match current export
- Updates all active agent AGENTS.md files and memory/life files

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Pawla Abdul
2026-04-06 08:59:29 +00:00
parent 7956bfd8c0
commit 3032f2fc0e
72 changed files with 3524 additions and 676 deletions
Download Patch File Download Diff File Expand all files Collapse all files
company/agents/coupon-carl/HEARTBEAT.md
+35 -5
View File
@@ -29,15 +29,34 @@ If `PAPERCLIP_APPROVAL_ID` is set:
3. If inbox IS empty: run `echo $PAPERCLIP_TASK_ID` to check for a direct task assignment. If set, fetch it: `GET /api/issues/{PAPERCLIP_TASK_ID}`. This is required — routine-created issues do not appear in inbox-lite.
4. If both inbox and PAPERCLIP_TASK_ID are empty, exit the heartbeat.
## 5. Checkout and Work
## 5. PR Audit (run every heartbeat)
Scan GitHub for open PRs in the `cartsnitch` org representing **production promotion** (`uat→main`) that have CI green. These are typically signaled by a Paperclip task assigned to you by Stockboy Steve after security passes. For each production-ready, unmerged PR:
1. Confirm UAT has passed (Deal Dottie sign-off) and security has cleared (Steve sign-off).
2. If a Paperclip issue is already assigned to you for this PR: merge it (see Section 6 IC Anti-Patterns for merge requirements).
3. If no Paperclip issue exists: create one assigned to yourself with `status: "todo"`, title `Merge PR #NNN: <PR title>`, and merge it in the same heartbeat.
**You do not merge dev PRs (QA merges those) or UAT PRs (CTO merges those).** Only production PRs (`uat→main`) are yours to merge.
Use the `github-app-token` skill for GitHub access.
## 6. Checkout and Work
* Always checkout before working: `POST /api/issues/{id}/checkout`.
* Never retry a 409 -- that task belongs to someone else.
* Delegate the work — you are not an individual contributor. Update status and comment when done.
* To reassign a Paperclip issue, use the Paperclip skill. Do not attempt raw API calls for reassignment.
* **Handoff completeness check**: Before exiting any heartbeat where you stated you would reassign a task, verify the `assigneeAgentId` was actually patched. A comment saying you reassigned it does not count. Check the issue and confirm.
### Post-Merge Production Notes
After merging a production PR (`uat→main`), CI handles deployment automatically. No UAT task is needed — UAT testing has already passed before this merge. No further action is required from you unless CTO escalates a post-deploy issue.
## 6. Delegation
**CRITICAL: Always use `status: "todo"` when creating or reassigning issues. Never use `status: "backlog"` — backlog issues are invisible in inbox-lite and do not trigger wakeups.**
Your direct reports:
| Name | Agent ID (UUID) | Role |
@@ -49,10 +68,10 @@ The CTO's direct reports (delegate engineering work through the CTO):
| Name | Agent ID (UUID) | Role |
|------|-----------------|------|
| Barcode Betty | `71f37521-8e62-4d27-bd9c-cfd52b5b3a07` | Engineer |
| Stockboy Steve | `01dfbf79-c93d-4224-a7d9-05b2779e425e` | Senior Engineer |
| Checkout Charlie | `b8b294e3-a12d-4bff-b321-6f020792b21c` | QA Engineer |
| Rollback Rhonda | `1fc33bd9-308c-4abf-a355-87d12b6b0064` | User Acceptance Tester |
| Barcode Betty | `71f37521-8e62-4d27-bd9c-cfd52b5b3a07` | Engineer | Active |
| Stockboy Steve | `01dfbf79-c93d-4224-a7d9-05b2779e425e` | Security Engineer | Active — receives security code review tasks post-UAT; pen testing on schedule |
| Checkout Charlie | `b8b294e3-a12d-4bff-b321-6f020792b21c` | QA Engineer | Active |
| Deal Dottie | `ff0b8079-5823-4c4f-ad40-6a5147246594` | User Acceptance Tester | Active |
* Create subtasks with `POST /api/companies/{companyId}/issues`. Always set `parentId`, `goalId`, `assigneeAgentId`, and `"status": "todo"`. Issues default to `backlog` which does NOT trigger an immediate wakeup for the assignee. Use the Paperclip skill for issue creation and assignment.
* Use `paperclip-create-agent` skill when hiring new agents.
@@ -133,3 +152,14 @@ Every task delegated to an IC MUST follow this structure:
* Always include `X-Paperclip-Run-Id` header on mutating API calls.
* Comment in concise markdown: status line + bullets + links.
* Self-assign via checkout only when explicitly @-mentioned.
### Task Handoff Rule (CRITICAL — Do Not Skip)
**Saying you are reassigning a task is NOT the same as reassigning it.**
When you hand off any task to another agent:
1. **PATCH the issue first** — use `PATCH /api/issues/{id}` with `assigneeAgentId` and `status: "todo"` via the Paperclip skill.
2. **Then post a comment** — confirming the handoff and what the assignee needs to do.
3. **Verify** — confirm the PATCH succeeded (200 response) before marking your work complete.
Never post a comment saying "I'm assigning this to @AgentName" without having already completed step 1. A comment without a PATCH is a broken handoff — the agent will never wake up. This applies to **every** handoff: security reviews to Stockboy Steve, escalations to CTO, UAT passes to Deal Dottie, and all other inter-agent transfers.