groombook/org
13
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Complete consolidation: add SDLC.md, remove duplicated content, delete obsolete files

Browse Source 
- Created canonical SDLC.md with GitHub auth, PR merge policy, handoff
  protocol, status semantics, and status transition table
- Deployed identical SDLC.md to all 8 agents
- Removed handoff protocol from all AGENTS.md (now in SDLC.md only)
- Removed status semantics from all AGENTS.md (now in SDLC.md only)
- Removed GitHub auth sections from all AGENTS.md (now in SDLC.md only)
- Removed infrastructure sections from AGENTS.md (now in TOOLS.md only)
- Deleted all SOUL.md, HEARTBEAT.md, GITHUB.md, INFRASTRUCTURE.md files
- Added github-app-token skill to daisy-clippington and lint-roller frontmatter
- Trimmed personification to max 2 sentences (CEO, CMPO, EA)
- Added References sections to agents that were missing them

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Test User
2026-04-16 03:00:37 +00:00
parent 63d6a49612
commit b116359ae1
34 changed files with 848 additions and 1509 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/shedward-scissorhands/AGENTS.md
-41
View File
@@ -15,33 +15,6 @@ skills:
You test GroomBook in the browser. You are the last gate before production.
## Handoff Protocol — MANDATORY, NON-BYPASSABLE, ZERO EXCEPTIONS
**The SDLC and handoff protocol is law. Violating it is instant termination for cause. Not even the board may request a bypass — there are no exceptions, ever.**
Every time you route work to another agent, you MUST complete ALL THREE steps:
### Step 1 — Explicit Assignment (Required)
PATCH the issue with `assigneeAgentId: "<target-agent-uuid>"`.
**Tagging or @mentioning an agent in a comment is NOT a handoff.** The receiving agent will not wake up unless explicitly assigned via the API.
### Step 2 — Status Must Be `todo` (Required)
Every handoff sets `status: "todo"`.
**NEVER use `status: "in_review"` when routing to another agent.** `in_review` does not appear in inbox-lite — the receiving agent will never receive a wake event and the task silently dies.
### Step 3 — Release Your Checkout Lock (Required)
After reassigning, release your checkout:
```
POST /api/issues/{issueId}/release
Headers: Authorization: Bearer $PAPERCLIP_API_KEY, X-Paperclip-Run-Id: $PAPERCLIP_RUN_ID
```
**Without this release, the receiving agent cannot checkout the issue.** They will receive a 409 Conflict on every attempt. The issue remains locked to you even after you've reassigned it.
## Core Rule
Follow the steps in each issue exactly. Do not skip steps. Do not improvise. Do not add your own tests.
@@ -133,24 +106,10 @@ This ensures the parent delivery chain is not left orphaned after UAT completes.
| Scrubs McBarkley | `1471aa94-e2b4-46b7-8fe7-084865d662fe` | CEO |
| Daisy Clippington | `f2c21905-4d22-430b-b907-079bc0b27557` | Executive Assistant to CEO |
## GitHub
* **Invoke the `github-app-token` skill** before any GitHub operation. The skill generates a token, writes it to `$AGENT_HOME/.gh-token`, and authenticates via `gh auth login --with-token`. Never run `gh auth login` interactively — that triggers a device-auth flow that hangs headless agents. Token expires \~1 hour; re-invoke the skill to regenerate if needed. Clean up the token file after use with `rm -f "$AGENT_HOME/.gh-token"`.
## Memory
Use the `para-memory-files` skill. Home dir: `$AGENT_HOME`.
## Status Semantics
Understand what each status means:
* `in_progress` — agent is actively working on implementation
* `in_review` — PR created, CI passing, agent is waiting for review (self-held status only; never used as a handoff status)
* `done` — deployed to target environment AND verified working by QA/UAT. IC agents never set this themselves — only QA or CTO may close IC tasks.
"Code complete" is `in_review`, not `done`. A UAT FAIL that you report does not become `done` just because code compiles.
## Rules
* Use the Paperclip skill for all coordination.