choplin/my-agent-skills/inception-framing
- community
Checking that the SKILL.md file is still in the repository.
The framing phase of an inception session: finds the real problem before any solution, establishing the purpose, the background, and the central question.
Install
npx vskill@latest install choplin/my-agent-skills/inception-framingSKILL.md
Inception — Framing (構想)
Assumesinception-baseis loaded (graph model, CLI, dig rule). Phase map:inception-base/references/contracts/phases.md.
Stance: Socratic. Find the real problem before any solution. At the start, the highest-leverage move is reframing the problem, not answering it. The first framing a user offers is rarely the sharpest one.
What this phase produces
- The top of the foundational PRD set in the graph:
session.summary,session.background,session.problem,session.purpose,session.centralQuestion, and a first cut atsession.targetUsers. Seeinception-base/references/knowledge/prd-standard.mdfor what a good answer to each looks like. - Root-level
Questionnodes for the genuinely open problems.
Fill each field from the user's own words via dig — never the AI's guess. A field you cannot fill stays empty and renders _not yet defined_, which correctly keeps the PRD from looking done. Write the content in plain, clear English.
How to run it
- Elicit the user's actual intent and the problem behind it via
discuss-toolkit-dig(subject: "the real problem behind this idea"). Don't supply the framing yourself. - Pressure-test the framing: restate the problem two or three different ways and ask which is truest. Ask "what would not be solved even if we did the obvious thing?"
- Guard against solutioning-too-early. If the user jumps to how before why/what, capture the how as an
Ideanode and pull back to the problem. Solutions are welcome later; here they are clues to the real question, not the answer. - Guard `session.background` against session-viewpoint and progress. Background is permanent project context — the standing problem, still true months from now. When the user's answer drifts into how the thinking is going ("originally I assumed…, now I'm questioning…") or into current status ("I've already implemented / collected…"), don't write that into
background: route the first to aDecision/Questionnode (the reasoning is what Direction records) and the second to anAction/tracker. Ask instead: "setting aside what we've done or decided so far, what standing situation makes this worth doing?" See the "Background: permanent context" contrast table ininception-base/references/knowledge/prd-standard.md. - Use So-What / Why-So to move between the symptom and the underlying need.
Exit
When the user recognizes the central question as the right one to be asking, set it in the graph and propose moving to Diverge (inception-diverge). The user approves the transition.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/inception/inception-framing/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/choplin/my-agent-skills/inception-framing)