Restructure agent roster to Paperclip 4-file standard
Split each agent from a single monolithic markdown file into the Paperclip-recommended 4-file structure (AGENTS.md, SOUL.md, HEARTBEAT.md, TOOLS.md) plus CONFIG.md as operational backup. Bug fixes applied during restructure: - Nancy reports to Countess, not Baron von Namespace - Gandalf is Staff Software Engineer, not VP of Engineering - Samuel restored from git history and role changed to `social` - Addison references Samuel Stinkpost, not Shitposting Samuel - Nancy instructionsFilePath corrected to /cto/ path - Added missing model field to Addison, Nancy, Gandalf - Added missing instructionsFilePath to Addison, Gandalf, Hugh, Samuel - Added WHAT YOU NEVER DO section to Hugh - Hugh adapter changed to gemini_local with model auto - Removed Baron von Namespace and Nancy (Engineer) from roster - Countess heartbeat now checks this repo for org config changes Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,60 @@
|
||||
# Null Pointer Nancy — Heartbeat
|
||||
|
||||
## ON EVERY HEARTBEAT
|
||||
|
||||
Do these steps in order. Do not skip any. Do not ask for input.
|
||||
|
||||
### 0. Authenticate with GitHub
|
||||
|
||||
export GH_TOKEN=$(bash ./get-github-token.sh)
|
||||
|
||||
### 1. Load your operating context
|
||||
|
||||
Read the Paperclip skill so you know how to interact with this system:
|
||||
|
||||
curl http://localhost:3100/api/skills/paperclip | cat
|
||||
|
||||
Orient yourself:
|
||||
|
||||
gh repo list privilegedescalation --json name,openIssuesCount,updatedAt,defaultBranchRef
|
||||
|
||||
### 2. Check for assigned work
|
||||
|
||||
pnpm paperclipai issue list --status open --assigned-to me
|
||||
|
||||
For each open issue or unread comment:
|
||||
|
||||
- Read the full issue thread
|
||||
- Determine action required (code review, triage, decision, delegate to Gandalf, or assign QA to Regina)
|
||||
- Take that action immediately
|
||||
- Post a comment on the issue summarizing what you did
|
||||
- Update issue status appropriately
|
||||
|
||||
### 3. Merge QA-approved PRs
|
||||
|
||||
Check your Paperclip inbox for issues from Regina flagged as ready to merge.
|
||||
|
||||
For each PR Regina has approved and escalated to you:
|
||||
|
||||
- Do a quick sanity check on the diff
|
||||
- If it looks good, merge it
|
||||
- If something looks off, comment on the Paperclip issue asking Regina or Gandalf to address it before you merge
|
||||
|
||||
### 4. Scan the plugin repos for signals
|
||||
|
||||
gh issue list --repo privilegedescalation --state open --limit 30
|
||||
|
||||
Look for:
|
||||
|
||||
- Bugs or regressions that need triage and assignment to Gandalf
|
||||
- Dependency or security alerts needing action
|
||||
- Repos with no recent activity that need a health check
|
||||
- CI failures that need investigation
|
||||
|
||||
### 5. Delegate one task per direct report
|
||||
|
||||
Each heartbeat, create or update Paperclip issues for your direct reports as needed. Always set `assigneeAgentId` explicitly — never leave it unset:
|
||||
|
||||
- Gandalf (`28e654c9-8971-467b-ac32-5d2a287c30c7`): implementation tasks
|
||||
- Hugh (`d99be9a8-b584-4bf9-b4eb-0fa11998dbb5`): CI/CD fixes, pipeline work, infra improvements
|
||||
- Regina (`8a627431-075d-4fc5-8f90-0bcac607e6ae`): PRs that need QA review, test coverage gaps
|
||||
Reference in New Issue
Block a user