本文へ移動
cccskills
無料GitHub で公開

domain-vision-interview

The quick interview that captures a Domain's or major Feature's minimal (go-live) and final vision verbatim into its VISION.md. Use when a node shows VISION MISSING, a registry domain is ratified without a vision, gap analysis lacks a go-live bar, or on /domain-vision-interview <domain>.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

<!-- SYNCED COPY — do not edit here. Canonical: common-docs/skills/domain-vision-interview/SKILL.md This file is distributed to every consuming repo by common-docs/meta/scripts/sync_skills.py. Edit the canonical, run the sync, and commit each repo. Edits made here are overwritten and lost. -->

domain-vision-interview — the minimal vision and the final vision

Arman, 2026-08-20 (verbatim in /systems/platform/docs-system/VISION.md): "An agent comes to me and does a quick interview, and it's a big picture interview where the agent essentially extracts from me the minimal vision for the particular module and then the final vision. So the minimal vision would be what we have to have before we can go live — because we're not in production yet, and we're being held up by all this stuff. And then what's like the ultimate goal of this thing — and capturing those and documenting them allows for agents to be able to do a much better job of doing gap analysis."

Disambiguation: this is NOT the platform's Vision Interview System (systems/masterwork/vision-interview/ — a Masterwork Approach, a product feature for users). This is an internal docs-system skill: a short conversation with Arman about one Domain.

Before the interview

  1. Confirm the target: one Domain (or one major Feature) from policies/domain-tree.md. One interview covers ONE node — never a menu of domains in one sitting.
  2. Do the homework HE shouldn't have to do: read the node's existing docs and skim its code anchors so your questions are informed. Collect any existing verbatim Arman quotes about it — the interview extends his record, never re-asks what is already settled (check the node's DECISIONS.md and the "settled — never re-ask" tables).
  3. Prepare and ask per the grilling skill, kept shallow on purpose. The MINIMAL bar and the FINAL vision both go in round 1 (both open-ended). No spec-depth branches.

The interview — two bars, big picture only

  • The MINIMAL vision: "What must this domain have, at minimum, before we can go live?" Chase it until it is a concrete, finite list in his words — the go-live bar. Push back gently on anything that sounds like final-vision scope creep ("is that needed to go live, or is that the destination?").
  • The FINAL vision: "When this system is fully grown, what is it?" Open-ended; let him talk; capture his words. (His own exemplar: the CMS is not a content tool — "it's a website platform… a replacement for Shopify, WordPress… web building and hosting and domain management.")
  • Stay big-picture: this is a quick interview, not a spec session. Details he volunteers are captured; details he doesn't are not chased.

After the interview

  1. Write the node's VISION.md (or extend it): two sections — Minimal vision (go-live bar) and Final vision — all verbatim, attributed, dated; inferences marked (inferred); nothing paraphrased. Update the registry node (vision recorded).
  2. Clear VISION MISSING wherever the node carried it (register Notes, handoffs).
  3. The gap analysis is now mechanical: the node's STATE.md pending list gets two flags — items required by the MINIMAL vision (go-live blockers) vs items serving only the FINAL vision. Surface the go-live set prominently; that is the whole point.
  4. Commit + push; end with the mandatory question: any (more) modifications to the skill or the core system?

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Admin debug system wiring for the floating AdminIndicator's live debug data and Copy Full Context. Use when adding debug visibility to a route or feature, wiring useDebugContext or the debug panel, capturing console errors, or enabling the copy-context workflow for a page.

日本語の概要は準備中です。原文の説明を表示しています。

armanisadeghi/ai-matrx32026年10月13日 更新

Compact two-icon Copy / Copy-for-AI controls (components/agent-copy). Use when adding copy buttons to a row, card, list, or record; merging duplicate Copy/JSON/AI controls; continuing the copy rollout; or writing a Copy-for-AI payload. NOT for markdown content actions (use rich-document-actions).

日本語の概要は準備中です。原文の説明を表示しています。

armanisadeghi/ai-matrx32026年10月13日 更新

Disclosing a surface's existing fixed AI jobs in the shell's top Agents menu. Use when a page, panel, overlay, or window already runs a mandate behind a button, assist, automatic action, or mode; when the agent-disclosure guard names a file; or during a surface check.

日本語の概要は準備中です。原文の説明を表示しています。

armanisadeghi/ai-matrx32026年10月13日 更新

The watch-fix-rerun method for making an existing platform agent or automated process efficient and correct: baseline its ledger, run one unit yourself, fix the class behind every wasted call, rerun, record. Use when asked to improve, optimize, watch, or 'make efficient' an agent, a sandbox session, a sync job, or any recurring automated process.

日本語の概要は準備中です。原文の説明を表示しています。

armanisadeghi/ai-matrx32026年10月13日 更新

Redux state for agent execution and firing agent shortcuts. Use when editing features/agents/redux/, building agent UI, creating a conversation, touching assembleRequest or NDJSON stream state, wiring agent-state selectors, adding a per-conversation capability, or triggering a shortcut from a button, menu, or code (useShortcutTrigger, launchAgentExecution).

日本語の概要は準備中です。原文の説明を表示しています。

armanisadeghi/ai-matrx32026年10月13日 更新

The provision for a call site: the exhaustive menu of values that place in the code can realistically produce. Use before creating or fixing a mandate or agent that reasons about more than its own input, when deciding whether an agent can answer at all with what it is sent, or when its output 'looks right' but nobody checked it could be. NOT for building the agent (use create-agent).

日本語の概要は準備中です。原文の説明を表示しています。

armanisadeghi/ai-matrx32026年10月13日 更新

armanisadeghi のスキルをすべて見る

このスキルの問題を報告する