interview
/interview
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan) WITHOUT needing their API key yet. Use when the user says "help me scope an agent", "I have an idea for an agent", "what should this agent be", or when the orchestrator routes phase=interview. Drives the six intake slots (job, trigger, inputs, actions, definition-of-done, recurrence) via AskUserQuestion, maps them to primitives with interview_planner.py, assembles build-sheet.json with build_sheet_builder.py, a
- Author
- alirezarezvani ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 3
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 3 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/build_sheet_builder.py, scripts/interview_planner.py, scripts/primitives_validator.py
What it does and when to use it
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan) WITHOUT needing their API key yet. Use when the user says "help me scope an agent", "I have an idea for an agent", "what should this agent be", or when the orchestrator routes phase=interview. Drives the six intake slots (job, trigger, inputs, actions, definition-of-done, recurrence) via AskUserQuestion, maps them to primitives with interview_planner.py, assembles build-sheet.json with build_sheet_builder.py, a
Triggers from the description
Original author description
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan) WITHOUT needing their API key yet. Use when the user says "help me scope an agent", "I have an idea for an agent", "what should this agent be", or when the orchestrator routes phase=interview. Drives the six intake slots (job, trigger, inputs, actions, definition-of-done, recurrence) via AskUserQuestion, maps them to primitives with interview_planner.py, assembles build-sheet.json with build_sheet_builder.py, a
How it works
- The six intake slots (ask one at a time; use AskUserQuestion for choices)
- Workflow
- Hard rules
- Forcing-question library (recommend + cite)
- Tools
SKILL.md preview
---
name: interview
description: Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan) WITHOUT needing their API key yet. Use when the user says "help me scope an agent", "I have an idea for an agent", "what should this agent be", or when the orchestrator routes phase=interview. Drives the six intake slots (job, trigger, inputs, actions, definition-of-done, recurrence) via AskUserQuestion, maps them to primitives with interview_planner.py, assembles build-sheet.json with build_sheet_builder.py, and validates limits with primitives_validator.py. Connectors are mockable in v0 (schema-true custom tools); real MCP servers become v1 deferrals. Distinct from stage-launch (which turns the sheet into payloads).
license: MIT
metadata:
version: 2.11.2
author: Alireza Rezvani
tags: [cma, interview, scoping, build-sheet, primitives, deferrals, eval-plan]
compatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]
---
# Phase 1 — Interview → Plan
Open warmly with one or two examples from
[`../../references/examples-bank.md`](../../references/examples-bank.md), then interview
the founder into a **build sheet**. No API key needed in this phase — the output
is a plan.
## The six intake slots (ask one at a time; use AskUserQuestion for choices)
| Slot | Question | Maps to |
|---|---|---|
| **Job** | "What one job should this agent do end-to-end?" | `agent.system` + outcome `description` |
| **Trigger** | "What kicks it off — you ask it, an event, or a schedule?" | on-demand / event / cron |
| **Inputs** | "What does it read?" (files, repo, memory, gmail/slack/github, web) | resources / MCP servers / memory |
| **Actions** | "What does it do?" (draft, write, call APIs, run code) | agent toolset / custom tools / MCP |
| **Done** | "How would you grade a good run?" | outcome `rubric` (required) |
| **Recurrence** | "Once, on request, or on a cadence?" | single-pass / grade-loop / cron-loop |
See [`../../references/interview-to-config.md`](../../references/interview-to-config.md)
for the full mapping.
## Workflow
1. **Interview.** Walk the six slots. Capture the founder's own words — never
invent specifics they didn't claim.
2. **Map to primitives.**
```bash
python3 scripts/interview_planner.py \
--job "Triage overnight support email" --trigger schedule \
--inputs "gmail,memory" --actions "label,reply" \
--dod "one label per email, grounded reason, no invented facts" \
--recurrence daily --out ./my-agent/plan.json
```
MCP inputs become **schema-true mock custom tools** in v0 and a **v1 deferral**
to wire the real server. Irreversible actions (send/publish) become **v2
deferrals** behind `always_ask`.
3. **Assemble the sheet.**
```bash
python3 scripts/build_sheet_builder.py --plan ./my-agent/plan.json --out-dir ./my-agent
```
4. **Validate limits.**
```bash
python3 scripts/primitives_validator.py --sheet ./my-agent/build-sheet.json
```
FAIL blocks progress; fix and re-run. WARN is advisory (surface it).
5. **Record the plan in the goal.** `goal_state.py set --phase stage-launch
--artifact build_sheet=./my-agent/build-sheet.json`, then advance.
## Hard rules
- **v0 is the core job only.** Everything else is a versioned deferral with a
reason and an exact mechanism.
- **Their problem, their words.**
- **No key yet.** The interview produces a plan; the key is a Phase-2 concern.
## Forcing-question library (recommend + cite)
1. "What one job — singular?" *Recommend:* the most-repeated task. *Cite:*
interview-to-config.md. Two jobs → two agents.
2. "Real integration or v0 mock?" *Recommend:* mock; wire MCP as v1. *Cite:*
interview-to-config.md rule 1.
3. "How do you grade it?" *Recommend:* 3–5 grounded rubric lines. *Cite:*
cma-primitives.md (rubric required).
4. "Smarter over time?" *Recommend:* attach memory only if yes. *Cite:*
cma-primitives.md (memory limits + injection).
5. "Once, or on a cadence?" *Recommend:* on-demand v0, schedule as Phase-4.
*Cite:* loops-and-workflows.md.
## Tools
- `scripts/interview_planner.py` — answers → primitives skeleton + deferrals.
- `scripts/build_sheet_builder.py` — assemble/normalize build-sheet.json.
- `scripts/primitives_validator.py` — validate vs CMA limits (PASS/WARN/FAIL).
Files in this package (5)
- README.md 1 KB
- SKILL.md 4 KB
- scripts/build_sheet_builder.py 4 KB
- scripts/interview_planner.py 8 KB
- scripts/primitives_validator.py 7 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · alirezarezvani/claude-skills | 100 | MIT |
| q00/ouroboros | 100 | MIT |
| vanducng/skills | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
| mthines/agent-skills | 100 | MIT |
| r3dlex/oh-my-auggie | 100 | Apache-2.0 |
| YuDefine/nuxt-supabase-starter | 100 | MIT |
| biliboss/skills | 100 | MIT |
| Soe-Reh/soes-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 9de4ab5fa4db (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100stage-launch
Phase 2 of building a Claude Managed Agent — turn a validated build sheet into exact API payloads and a resumable BYOK curl launch script, then launch (environment → agent → session → kickoff) using the founder's OWN Anthropic key. Use when the user says "launch it", "deploy the… - 100launch-your-agent
Help a technical founder build whatever they want on Claude Managed Agents — an internal worker, a piece of their product, a customer-facing agent. Find out what they want to build, scope a v0, launch it in their account, grade it, iterate, and (if it should run on a clock) put… - 100agent-launcher-orchestrator
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a managed agent", "run this on a schedule", "grade my agent against a rubric", "set up a nightly worker". Reads the… - 95ultraapp-interview
Use when the user opens a Forge tab in the claw-orchestrator dashboard to start building a new ultraapp. Drives a structured Q&A interview that produces a complete AppSpec, then signals readiness to build. - 100claude-managed-agents-webhooks
Receive and verify Anthropic Claude Managed Agents (CMA) webhooks. Use when setting up Claude Managed Agents webhook handlers, debugging signature verification, or handling agent session and vault events like session.status_idled, session.status_terminated,… - 100oc-create-agent
Guides through creating a new OpenCode-compatible agent with interactive interview, permission configuration, and validation. Use when user says "create opencode agent", "new opencode agent", "build agent for opencode", or wants to create an OpenCode agent markdown file.