hiring-brief
Skill4 starsChanged 4 months agoMITView on GitHub
CEO skill for chartering a NEW agent role in a Paperclip org — mission fit, responsibilities and boundaries, attached skills list, monthly budget, definition of done for the first 3 tickets, and 1-week probation review criteria. Use when the org needs a new specialist, when the CEO says "we need someone to own X", "charter a new agent", "hire a [role] agent", or workload evidence shows a capability gap. Don't use for routing tickets to agents that already exist — that's delegation-protocol.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- GTMify/aigtmtheir own version, first seen May 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- GTMify/aigtm★ 25same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository74 other files it gives its agents.
- agent-eval-harnessSkill
- context-budget-managerSkill
- incident-rollbackSkill
- memory-hygieneSkill
- model-cost-optimizerSkill
- prompt-debuggerSkill
- skill-author-coachSkill
- third-party-skill-vetterSkill
- api-endpoint-testerSkill
- bug-triage-protocolSkill
- changelog-release-notesSkill
- docs-readme-writerSkill
- env-secrets-hygieneSkill
- github-pr-reviewSkill
- git-ship-flowSkill
- lovable-brief-writerSkill
- supabase-migration-writerSkill
- vercel-deploy-checkSkill
- cold-outreach-sequencerSkill
- competitor-pricing-scanSkill
- contract-redline-scanSkill
- customer-support-inboxSkill
- invoice-runnerSkill
- kpi-dashboard-weeklySkill
- lead-research-dossierSkill
- payment-reconciliationSkill
- pipeline-trackerSkill
- proposal-builderSkill
- stripe-payment-linkSkill
- testimonial-harvesterSkill
- weekly-revenue-reportSkill
- brand-voice-guardianSkill
- case-study-builderSkill
- content-repurposerSkill
- deep-research-briefSkill
- email-nurture-sequenceSkill
- landing-page-copywriterSkill
- linkedin-content-packSkill
- newsletter-assemblerSkill
- seo-blog-writerSkill
- social-listening-reportSkill
- x-thread-builderSkill
- youtube-script-writerSkill
- budget-guardrailsSkill
- ceo-operating-doctrineSkill
- delegation-protocolSkill
- editor-personaSkill
- heartbeat-standupSkill
- ops-agent-personaSkill
- researcher-personaSkill
- sales-agent-personaSkill
- support-agent-personaSkill
- weekly-retroSkill
- writer-personaSkill
- calendar-conciergeSkill
- decision-journalSkill
- email-triageSkill
- file-organizerSkill
- habit-trackerSkill
- inbox-zero-sprintSkill
- The first 60 shown.
The file
Files
Hiring Brief
A CEO-only skill: charter a new agent role so completely that the agent can succeed from ticket one — or prove within a week that the role shouldn't exist. Every hire traces to the mission, arrives with skills attached and a hard budget, gets 3 first tickets with definitions of done, and faces a probation review with pass/fail criteria written before day one. No charter, no hire.
When to Use
- Recurring work has no owner and evidence (tickets, standups, retro items) shows the gap is real.
- The human directs the org to add a capability (sales, support, ops, editorial...).
- An existing agent is chronically overloaded and the overflow is a coherent role, not just volume.
- Not for: assigning work to existing agents (
delegation-protocol), adjusting an existing agent's budget (budget-guardrails), or spinning up a throwaway agent for a single task (delegate the ticket instead — hires are for recurring ownership).
Role Boundary
- The CEO owns: drafting the charter, mission-fit justification, skill selection, first-ticket design, probation criteria, and the probation verdict recommendation.
- The CEO escalates to the human: final approval of every hire (headcount changes org cost — human signs off), any budget that changes the org's total monthly cap, roles touching money/legal/sending scopes, and the probation fail decision (recommend, human confirms).
- Never: hire without a written charter, grant a new agent send/spend authority in v1, or let a probation week pass without its review.
Quick Reference
| Action | Rule |
| Mission fit | Charter states the ancestry the role serves: mission → goal(s) → the projects it will own tickets in |
| Evidence bar | ≥3 concrete instances (tickets/standup items) showing the unowned recurring need |
| Skills list | Named skills from the repo attached at charter time; missing skill = flagged authoring gap, not a vague "will figure it out" |
| Budget | Hard monthly cap within org total; probation month set lean; no send/spend authority in v1 |
| First 3 tickets | Real work, ascending difficulty, each with a definition of done written in the charter |
| Probation | 1 week; pass/fail criteria fixed before start; review happens on schedule, verdict to human |
Procedure
- Prove the gap — collect ≥3 concrete instances of the unowned need (dropped tickets, standup complaints, retro items, overflow from a named agent). If you can't find 3, the answer is a delegated ticket, not a hire — stop here.
- State mission fit — one paragraph: which goal(s) this role advances, which projects it will own tickets in, and what measurably improves if the role works. A role you can't tie into the ancestry chain is an org vanity hire; don't charter it.
- Define the role boundary — owns / escalates / never, in the same shape as the existing personas (
writer-persona,support-agent-personaare the pattern). Check overlap against every current agent; any shared surface gets an explicit tiebreak rule in the charter. - Attach skills — list the exact repo skills the agent gets (persona skill + protocol skills:
delegation-protocol,budget-guardrails,heartbeat-standupare near-universal). A capability with no matching skill becomes a flagged authoring task with an owner — the agent doesn't start with an undefined capability. - Set the budget — hard monthly cap that fits inside the org total per
budget-guardrails; probation month set lean. State what happens at 80% (flag) and 100% (stop + report). v1 gets no send or spend authority regardless of role. - Design the first 3 tickets — real backlog items, ascending difficulty: (1) a bounded solo task, (2) a task requiring one hand-off with another agent, (3) a task at the role's expected complexity. Each gets a written definition of done (deliverable, quality bar, where it's posted, deadline).
- Write probation criteria — pass/fail checks for the 1-week review, fixed now: all 3 tickets done to definition, escalation behavior correct (escalated what it should, didn't over-escalate), budget respected, standups on time. Add one role-specific quality check.
- Approve & launch — present the charter to the human for sign-off (headcount + budget = human decision). On approval: create the agent, attach skills, assign ticket 1, and schedule the probation review with the criteria pre-loaded.
- Run the review — at the week mark, score criteria mechanically, recommend pass / extend-one-week (once, max) / dissolve, and hand the verdict to the human with evidence. A dissolved role's charter and review get filed as a retro lesson.
Output Template
# Hiring Brief: {role-name} agent
**Status:** draft → human-approval → live → probation-review
## Mission fit
Serves: {mission → goal(s) → projects} | Evidence of need: {3+ linked instances}
Success looks like: {measurable change}
## Role boundary
Owns: ... | Escalates: ... | Never: ...
Overlap tiebreaks: {vs existing agent → rule}
## Attached skills
{skill list} | Authoring gaps: {skill to write + owner, or "none"}
## Budget
Monthly cap: {amount} | 80%: flag CEO | 100%: stop + report | Send/spend authority: none (v1)
## First 3 tickets
| # | Ticket | Definition of done | Deadline |
|---|---|---|---|
## Probation review — {date, +1 week}
- [ ] 3/3 tickets to definition of done
- [ ] Escalation behavior correct (no misses, no noise)
- [ ] Budget ≤ cap, burn reported in standups
- [ ] Standups on time, honest about slips
- [ ] {role-specific quality check}
Verdict: pass / extend (once) / dissolve → human confirmsPitfalls
- Hiring instead of delegating — a one-off task gets a whole chartered agent, and the org accretes headcount that burns budget forever. Recovery: apply the step 1 evidence bar honestly; fewer than 3 recurring instances → route the work as a ticket and archive the draft charter.
- Vague definition of done — ticket 1 says "improve our outreach" and probation week ends in a judgment call nobody can defend. Recovery: rewrite each DoD until a third party could verify it (deliverable, location, quality bar, date); un-verifiable DoD blocks launch.
- Boundary collision — the new role and an existing agent both believe they own a surface, and tickets ping-pong. Recovery: run the step 3 overlap check against every persona; write the tiebreak into BOTH charters before launch.
- Probation theater — the week passes, everyone's busy, the agent stays by default with criteria unscored. Recovery: the review is a scheduled ticket created at launch with criteria attached; unscored probation = extend once and score properly, never silent-pass.
- Budget as a suggestion — the new agent's cap exists on paper while spend flows unmonitored. Recovery: wire the cap through
budget-guardrailsat creation; first standup must include burn-vs-cap or the hire isn't correctly launched.
Verification
- Evidence of need: ≥3 linked instances in the charter
- Mission fit paragraph ties the role into mission → goal → project ancestry
- Role boundary (owns/escalates/never) written, with overlap tiebreaks against existing agents
- Every attached skill exists in the repo, or the gap has a named authoring owner
- Hard budget cap set inside org total; no v1 send/spend authority
- 3 first tickets each carry a third-party-verifiable definition of done
- Probation review scheduled at launch with pass/fail criteria fixed; human sign-off recorded before the agent goes live
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

