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, 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
- 最近更新
- 2026-08-25
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- interview
- tags
- [ "cma", "interview", "scoping", "build-sheet", "primitives", "deferrals", "eval-plan" ]
- author
- Alireza Rezvani
- license
- MIT
- version
- 2.11.2
- 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).
- compatible_tools
- [ "claude-code", "codex-cli", "cursor", "antigravity", "opencode", "gemini-cli" ]
03 SKILL.md 正文
Phase 1 — Interview → Plan
Open warmly with one or two examples from
../../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
for the full mapping.
Workflow
- Interview. Walk the six slots. Capture the founder's own words — never invent specifics they didn't claim.
- Map to primitives.
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 behindpython3 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.jsonalways_ask. - Assemble the sheet.
python3 scripts/build_sheet_builder.py --plan ./my-agent/plan.json --out-dir ./my-agent - Validate limits.
FAIL blocks progress; fix and re-run. WARN is advisory (surface it).python3 scripts/primitives_validator.py --sheet ./my-agent/build-sheet.json - 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)
- "What one job — singular?" Recommend: the most-repeated task. Cite: interview-to-config.md. Two jobs → two agents.
- "Real integration or v0 mock?" Recommend: mock; wire MCP as v1. Cite: interview-to-config.md rule 1.
- "How do you grade it?" Recommend: 3–5 grounded rubric lines. Cite: cma-primitives.md (rubric required).
- "Smarter over time?" Recommend: attach memory only if yes. Cite: cma-primitives.md (memory limits + injection).
- "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).
04 同仓库更多 Skills
webmcpify
Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for "webmcpify", "add WebMCP", or "expose app actions to AI agents".
vardoger-analyze
Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~/.copilot/session-state/`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~/.copilot/copilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.
transloadit-media-processing
Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS/MP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.
terraform-azurerm-set-diff-analyzer
Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.
technical-job-search
Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV/resume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.
steno-mode
Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says "steno mode", "shorthand mode", "compressed responses", "token reduction", "brief structured output", or invokes /steno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding/tutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.