interview
Interview the user relentlessly about a plan or design. Use when the user wants to plan/design a system, break down a problem, or asks an open question.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Interview the user relentlessly about a plan or design. Use when the user wants to plan/design a system, break down a problem, or asks an open question.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Use when handed a set/batch of iterations, plans, or work slices to carry out end to end in one run — multiple iteration/story IDs to execute, ordered by blocking edges, each with review, commit, and doc-status transitions, until the whole set is done. lazyspec or any DAG-backed backlog.
You MUST use this skill when authoring an iteration, work slice, or "iteration document" that hands a bounded unit of work to a coding agent — drawn from a story, card, spec, or backlog. Symptoms include an iteration that bundles several acceptance criteria, restates a spec it links to, or won't finish in one agent session.
You MUST use when writing a story/user story; when decomposing a system, feature, epic, requirement, or spec into a backlog of user stories, or whenever about to write user stories or acceptance criteria during planning. Symptoms include "break this into stories", "write the backlog", "split this epic", stories that feel too big to estimate, or technical tasks masquerading as stories.
You MUST use this skill any time you are investigating a bug/unintended behaviour, before proposing fixes
Use when comparing a running web UI against its intended design (Figma mockups or reference screenshots), reviewing visual/layout/spacing/typography fidelity of a page, component, or interaction, or when a design-vs-build diff is needed before shipping or to feed a fix loop.
Use when adding, installing, upgrading, or pinning a package/library in any language, choosing which version to use, or when install commands fail with externally-managed-environment, SSL/certificate, DNS (gaierror), or connection errors inside a sandbox.
| name | interview |
| description | Interview the user relentlessly about a plan or design. Use when the user wants to plan/design a system, break down a problem, or asks an open question. |
Help me think through and break down this plan in detail.
Start by mapping the problem: enumerate the key decisions this plan requires, ordered so decisions that others depend on come first. Show me this decision tree before asking anything — this is the breakdown, and keep it updated as new decisions surface.
Then interview me relentlessly, one decision at a time, walking down each branch and resolving dependencies as we go.
For each decision, before I answer:
Ask about one decision at a time; multiple at once is bewildering.
If a decision can be resolved by exploring the codebase, explore it instead of asking.