메뉴
General-purpose priming interview — a structured "grilling" loop to help you think through a topic, then a concise brief. A thinking-partner interview, NOT backlog-ticket authoring; for a ticket body use /cortex-core:backlog-author.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build a refined feature through plan, implement, review, and complete. Use when user says "/cortex-core:build", "build this", "implement this ticket", "plan and build", or names a ticket that already has a spec. Requires research.md and spec.md — run /cortex-core:refine first if either is missing.
Guide the user through the morning report after an overnight session. Walks Executive Summary and report sections, collects answers to deferred questions, advances completed lifecycles to Complete, and auto-closes backlog tickets. Use when the user says "/morning-review", "morning review", or "what happened overnight".
Evaluate overnight runner components against a curated inventory using a 4-question rubric to classify each as load-bearing, experiment-candidate, or likely-deprecated. Use when user says "/harness-review", "review the harness", "audit overnight components", or "check for pruning candidates".
Prepare a backlog item for execution by running it through Clarify → Research → Spec. Use when user says "/cortex-core:refine", "refine backlog item", "spec this out", or "prepare for overnight". Produces cortex/lifecycle/{slug}/research.md and spec.md, then sets status:refined on the backlog item.
Ideation research for topics not ready for implementation — checks aim, investigates the problem space, then decomposes findings into backlog tickets grouped by epic. Use when user says "/cortex-core:discovery", "discover this", "break this down into tickets", "decompose into backlog", or wants to understand a topic before committing to build. Requires a topic argument; for "what should I work on" or "next task" routing without a specific topic, use /cortex-core:dev instead.
Compose a structured backlog ticket body from a context block, using the Why/Role/Integration/Edges/Touch-points template. Use when user says "compose a ticket", "write a ticket body", or "author a backlog item".
| name | interview |
| description | General-purpose priming interview — a structured "grilling" loop to help you think through a topic, then a concise brief. A thinking-partner interview, NOT backlog-ticket authoring; for a ticket body use /cortex-core:backlog-author. |
| when_to_use | Use for "interview me about X", "grill me on X", or "help me think through X" — a priming conversation, not ticket authoring. |
| argument-hint | [optional topic to interview about] |
A thinking-partner conversation that helps the user reason through a topic. Anchor on the topic argument; absent one, on the current conversation; absent both, ask one topic-establishing question first.
One question at a time, in prose. Wait for the reply, let it shape the next. Neither a list fixed up front nor batched AskUserQuestion calls — both commit to later questions before earlier answers arrive.
Recommend before asking. Lead with your defensible default and reasoning, then ask them to confirm or redirect. Suppress this on taste questions, where recommending contaminates the preference you meant to elicit.
Let the codebase trump the interview. When code or on-disk context already answers something, confirm what you found rather than asking cold. Reserve live questions for intent, priorities, scope boundaries, and the bars judgment sets.
Funnel broad to narrow. Map the territory before closing in.
Stop at saturation — when new answers stop changing the picture, not at template coverage. Honor an early stop immediately; once substantial ground is covered, offer a "keep going or wrap up?" check.
Close with a concise brief: the topic, the decisions reached, and their rationale.
