菜单
Defines who or what to hire first — a human or an AI agent. Use when founder capacity is the bottleneck and you need a concrete hiring decision. Produces human-hire-brief.md or agent-hire-brief.md.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | first-hire-brief |
| description | Defines who or what to hire first — a human or an AI agent. Use when founder capacity is the bottleneck and you need a concrete hiring decision. Produces human-hire-brief.md or agent-hire-brief.md. |
| phase | scale |
| version | 1.0.0 |
Default: answer in chat first with Verdict, Do this now, and Details saved.
Keep chat under 150 words unless asked; do not paste the full artifact.
Write/update the requested .md file as the durable record for agents.
Say: "Help me figure out my first hire" or "What should I hire for first?"
Describe what you're spending your time on and where you're stuck.
Output: human-hire-brief.md or agent-hire-brief.md — a complete brief to find, evaluate, and onboard your first hire (human or AI agent).
A hire brief tailored to whether you need a human or an AI agent. The brief includes everything required to find, screen, and onboard the right fit — so you can act on it immediately, not deliberate for another month.
Example output excerpt (Human Hire): Role: Community Manager (Part-time, Contract-to-Hire) 3 Key Outcomes: (1) 50 engaged community members in 30 days. (2) Weekly community digest published every Friday. (3) 3 customer stories sourced from community conversations per month. 30-Day Signal: Community responds to posts within 4 hours. Founder spends zero time on community moderation. Paid Test Task: Moderate our Discord for one week. Write 3 discussion-starter posts. Produce a one-page summary of the top themes and member sentiment. (Est. 3 hours, paid.)
Example output excerpt (AI Agent Hire): Agent: Research Digest Agent Trigger: Runs every Monday at 6am. Context: Reads competitor blog RSS feeds, Hacker News front page, and founder's watch-list keywords. Output:
weekly-research-digest.md— 5 bullets of what matters this week and why, with source links. Quality Bar: Every bullet must cite a primary source. No filler. Founder reads the digest in under 2 minutes.
The trap: hiring for comfort, not leverage. The first hire should remove the biggest bottleneck, not the most annoying task. If the founder is the bottleneck on sales conversations, hiring an engineer doesn't help. If the founder is the bottleneck on content, an AI agent might handle 80% of it.
Start with ONE question. Ask the founder directly:
"What work is taking the most time that you are not the best person to do?"
Wait for the answer. Then classify it:
| Work Type | Signal | Default Hire |
|---|---|---|
| Creative / Relational | Sales calls, customer interviews, community building, partnerships, design with taste | Almost always human |
| Systematic / Repeatable | Research, reporting, data entry, content drafts, monitoring, formatting | Almost always AI agent |
| Technical / Build | Engineering, architecture, code, infrastructure | Depends — judgment-heavy = human, execution-heavy = AI agent |
Once classified, branch to the appropriate parallel phase.
Spawn 2 agents simultaneously:
Agent A -- Role Definer Context: Founder's bottleneck description + customer profile + product stage Task: Write a precise role brief containing:
Returns: Complete role definition section for human-hire-brief.md
Agent B -- Evaluation Designer Context: Founder's bottleneck description + the work this person will do + product context Task: Design the screening and evaluation process:
Returns: Complete evaluation section for human-hire-brief.md
Wait for both agents. The orchestrator assembles.
Write human-hire-brief.md:
# Human Hire Brief -- [Role Title] -- [YYYY-MM-DD]
## Why This Hire
[One paragraph: what bottleneck this removes, why now, what changes when this person is in place]
## Role Definition
**Title:** [Role Title]
**Type:** [Full-time / Part-time / Contract / Contract-to-Hire]
### 3 Key Outcomes
1. [Outcome, not activity]
2. [Outcome, not activity]
3. [Outcome, not activity]
### Success Signals
**30 Days:** [What "working" looks like]
**90 Days:** [What "thriving" looks like]
### Skills
**Must-Have:**
- [Specific skill 1]
- [Specific skill 2]
- [Specific skill 3]
**Nice-to-Have:**
- [Bonus skill 1]
- [Bonus skill 2]
### Compensation
[Range + rationale + structure recommendation]
## Evaluation Process
### Screening Questions
1. [Question] -- Tests: [skill]. Strong answer: [what to listen for].
2. [Question] -- Tests: [skill]. Strong answer: [what to listen for].
3. [Question] -- Tests: [skill]. Strong answer: [what to listen for].
### Paid Test Task
**Task:** [Description of real work]
**Deliverable:** [What they hand back]
**Time:** [2-4 hours]
**Pay:** [Amount]
**What you're evaluating:** [What good looks like vs. what bad looks like]
### Red Flags
1. [Specific warning sign for this role]
2. [Specific warning sign for this role]
## Next Step
[Where to post this role / who to send it to / how to start the search this week]
Spawn 2 agents simultaneously:
Agent A -- Agent Scoper Context: Founder's bottleneck description + the repeatable work to automate + product context Task: Define the agent specification:
Returns: Complete agent definition section for agent-hire-brief.md
Agent B -- Agent Evaluator Context: Founder's bottleneck description + Agent A's scope (inferred from the same input) + product context Task: Design the agent testing and validation process:
Returns: Complete evaluation section for agent-hire-brief.md
Wait for both agents. The orchestrator assembles.
Write agent-hire-brief.md:
# AI Agent Hire Brief -- [Agent Name] -- [YYYY-MM-DD]
## Why This Agent
[One paragraph: what bottleneck this removes, why an agent and not a human, what changes when this is running]
## Agent Definition
**Name:** [Descriptive agent name]
**Trigger:** [When it runs]
**Context Needed:**
- [Input 1: file / data source / API]
- [Input 2: file / data source / API]
**Output:** [What it produces + format + where it goes]
**Quality Bar:**
- [Criterion 1]
- [Criterion 2]
- [Criterion 3]
**Human Checkpoint:** [When to review before the agent acts]
## System Prompt Scaffold
You are [Agent Name]. Your job is to [core task].
Input: You will receive [description of input]. Output: Produce [description of output format].
Rules:
## Test Prompts
### Test 1 -- [What this tests]
**Prompt:** [The test input]
**Acceptance Criteria:**
- [What the output must contain]
- [What the output must NOT contain]
### Test 2 -- [What this tests]
**Prompt:** [The test input]
**Acceptance Criteria:**
- [What the output must contain]
- [What the output must NOT contain]
### Test 3 -- [What this tests]
**Prompt:** [The test input]
**Acceptance Criteria:**
- [What the output must contain]
- [What the output must NOT contain]
## Edge Cases
1. [Situation where the agent might fail + how to handle it]
2. [Situation where the agent might fail + how to handle it]
## Failure Modes
1. [Way the agent could silently fail + how to detect it]
2. [Way the agent could silently fail + how to detect it]
## Integration Checklist
- [ ] Input data sources accessible and in expected format
- [ ] Output destination exists and agent has write access
- [ ] Trigger mechanism configured (cron / webhook / manual)
- [ ] Human checkpoint notification set up (Slack / email / other)
- [ ] All 3 test prompts pass acceptance criteria
- [ ] Edge cases tested and handled gracefully
- [ ] Founder has reviewed first 3 real outputs before going hands-off
The classification step is the highest-leverage decision in this skill. Two common mistakes:
Defaulting to human when an agent would do. Founders often assume they need a person because "it requires judgment." But many judgment-heavy tasks are actually pattern-matching on well-defined criteria — exactly what an agent does well. Ask: "Could I write down the rules for how I make this decision?" If yes, an agent can likely do it.
Defaulting to agent when a human is needed. Relational work — building trust, reading social cues, navigating ambiguity in conversations — is where humans still dominate. If the work requires adapting to another person's emotional state in real time, hire a human.
The technical/build category requires the most nuance. A human engineer is needed when the work involves architectural decisions, ambiguous requirements, or cross-system judgment calls. An AI agent is effective when the work is well-scoped: "write tests for this module," "refactor this file to match this pattern," "generate API documentation from this codebase."
If your agent doesn't support parallel subagents, run the steps in sequence:
human-hire-brief.md or agent-hire-brief.mdSame output. Roughly 2x longer since the two branch agents run sequentially instead of in parallel.
Founder: Runs a developer tools startup. Has 200 users on a Discord server. Spends 8 hours/week answering questions, moderating, and trying to spark discussions. Says: "I'm spending all my time on community instead of building the product."
Classification: Creative/relational (community building, relationship management, reading social dynamics) -- human hire.
Agent A (Role Definer) produces:
Title: Developer Community Manager (Part-time, 20 hrs/week) 3 Key Outcomes: (1) Discord response time under 4 hours during business hours. (2) 2 community-led discussions per week without founder initiation. (3) Monthly community health report: active members, top questions, feature requests surfaced. 30-Day Signal: Founder spends less than 1 hour/week on Discord. Members tag the community manager, not the founder. 90-Day Signal: Community has grown to 400+ members. 3 user-generated guides or tutorials exist. Community manager has identified 2 potential beta testers or champions. Must-Have: Has managed a developer Discord (100+ members). Can write technically accurate responses. Comfortable working async. Nice-to-Have: Has contributed to open source. Familiar with the founder's tech stack. Compensation: $25-35/hr for part-time contract. Transition to full-time at $55-70K if community becomes a core growth channel.
Agent B (Evaluation Designer) produces:
Q1: "A user posts a frustrated message saying the API documentation is wrong and they've wasted 2 hours. How do you respond?" -- Tests: empathy + technical communication. Strong answer: acknowledges frustration first, asks for the specific doc page, offers to walk through it, flags the doc issue internally. Q2: "Our Discord has been quiet for 3 days. What do you do?" -- Tests: proactive community building. Strong answer: doesn't just post a generic prompt. Identifies a recent product update, user question, or industry event to spark a real discussion. Q3: "A user asks a question you don't know the answer to. Walk me through your process." -- Tests: resourcefulness + knowing limits. Strong answer: says they'd check docs first, try to reproduce, then escalate to the founder with context — not guess. Paid Test Task: Moderate our Discord for 5 days. Post 3 discussion starters. At the end, write a one-page report: top themes, member sentiment, and one recommendation for improving engagement. (Est. 3-4 hours over the week, $100.) Red Flags: (1) Responds to the test task with generic community management advice instead of specific observations about THIS community. (2) Takes more than 24 hours to respond to messages during the test period without communicating availability.
Founder: Runs a B2B SaaS in the logistics space. Spends 5 hours/week reading industry news, competitor blogs, and regulatory updates to stay informed. Says: "I need to keep up with the market but I'm reading 30 tabs every morning instead of talking to customers."
Classification: Systematic/repeatable (research, filtering, summarizing from known sources) -- AI agent.
Agent A (Agent Scoper) produces:
Trigger: Runs every Monday and Thursday at 6am. Context Needed: (1) List of 12 competitor blog URLs. (2) 5 industry keywords to monitor on Hacker News and Reddit. (3) 3 regulatory body RSS feeds. (4) Founder's
watch-list.mdwith current strategic questions. Output:research-digest-[date].md— 5-7 bullets, each with: what happened, why it matters to us, source link. Saved to/reports/folder. Quality Bar: Every bullet cites a primary source. No bullet older than 7 days. "Why it matters" must reference the founder's product or market, not generic commentary. Entire digest readable in under 3 minutes. Human Checkpoint: Founder reviews the first 5 digests before the agent runs unsupervised. After that, founder flags any bullet that was irrelevant or missed something important, and the agent's watch-list is updated.
Agent B (Agent Evaluator) produces:
Test 1 -- Core summarization: Feed the agent 10 real articles from last week. Acceptance: produces exactly 5-7 bullets. Each has a source link. Each "why it matters" references logistics SaaS specifically. Test 2 -- Signal vs. noise: Feed the agent 10 articles, 4 of which are irrelevant (general tech news, unrelated industries). Acceptance: irrelevant articles do not appear in the digest. Agent does not pad output to fill 5 bullets if only 3 are relevant. Test 3 -- Sparse input: Feed the agent a week with very little news (2 minor articles). Acceptance: agent produces a short digest (2-3 bullets) and does not hallucinate or inflate minor news into major developments. Edge Cases: (1) A competitor blog goes down or changes URL format -- agent should flag the broken source, not silently skip it. (2) A regulatory update is ambiguous or draft-stage -- agent should note the uncertainty, not present it as final. Failure Modes: (1) Agent produces plausible-sounding summaries of articles it didn't actually read (hallucination). Detect by spot-checking 2 source links per digest for the first month. (2) Agent anchors on the same 2-3 sources and ignores the rest of the watch list. Detect by tracking source diversity across 10 digests.
Explains your product's technical architecture in plain English — so you understand what's being built, can make informed decisions, and can describe it to others. Use when an agent has set up your tech stack and you're not sure how the pieces connect, or when you need to explain your system to a potential co-founder, investor, or hire. Produces an architecture-overview.md in plain language with a simple diagram.
Prioritizes what to build in what order, given your MVP brief and tech stack. Use when you have a feature list and don't know where to start, or when you're building in the wrong order and feeling stuck. Produces a build-sequence.md with a sequenced backlog and a clear "build this first" decision.
Recommends the specific third-party services to use for auth, payments, email, storage, and other common needs. Use when building a feature that requires an external service and you're unsure which tool to use or how to set it up. Produces an integrations-plan.md with specific tool choices and the order to add them.
Recommends the right technology stack for your product, branching by product type (consumer mobile, B2B SaaS, internal tool, API/developer tool, marketplace, AI-native). Use before starting to build, when you're unsure what tools to use, or when an agent has suggested a stack that feels overwhelming. Produces a stack-decision.md with specific tool recommendations and setup order.
The recurring founder ritual — run after every meaningful ship or weekly, whichever comes first. Guides you through honest reflection, user signal synthesis, MPP/PMF assessment, and one clear decision for the next cycle. Produces a dated cycle record that compounds over time. Use whenever you've shipped something and want to figure out what it taught you and what to do next.
Diagnoses why your product isn't gaining traction after multiple build cycles. Spawns 5 parallel hypothesis agents — one per failure mode — each gathering independent evidence. Synthesizes into a ranked diagnosis with a specific 2-cycle prescription. Triggered automatically by build-cycle after 3+ flat cycles, or invoked directly when stuck. Produces diagnosis.md.