القائمة
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 المهني
Structured feature development lifecycle with phases for research, specification, planning, implementation, review, and completion. Use when user says "/cortex-core:lifecycle", "start a lifecycle", "lifecycle research/specify/plan/implement/review/complete", "start a feature lifecycle", or wants to build a non-trivial feature with structured phases.
Development entry point that analyzes requests and routes to the appropriate workflow. Use when user says "/cortex-core:dev", "what should I work on", "start working on", "dev hub", "where do I start", "next task", "what's next", or describes a feature without naming a specific skill.
Prepare a backlog item for execution by running it through Clarify → Research → Spec. Use when user says "/cortex-core:refine", "refine backlog item", "prepare for overnight", or "prepare feature for execution". Produces cortex/lifecycle/{slug}/research.md and cortex/lifecycle/{slug}/spec.md, then sets status:refined on the backlog item.
Parallel research orchestrator. Use when the user says "/cortex-core:research", "research this topic", "investigate this feature", or when /cortex-core:refine delegates its research phase. Dispatches 3–10 parallel agents across independent angles, synthesizes into research.md or conversation output.
Create git commits with consistent, well-formatted messages. Use when user says "commit", "/cortex-core:commit", "make a commit", "commit these changes", or asks to save/checkpoint their work as a git commit.
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".
| 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.
