Examine a plan, decision, or idea through structured rounds of questions. Map which decisions depend on others, offer a recommendation for each question, and keep exploring until the user confirms a shared understanding before action begins.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Interview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.
Work the tree in rounds. The frontier is every decision whose prerequisites are already settled — the questions you can ask now without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
Each question should be formatted like so:
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
Each round the user answers reshapes the tree — settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a later round, not this one.
Finding facts is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it — don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report — ask the rest of the frontier now. The decisions are the user's — put each to them and wait.
The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Turn an initial idea into an agreed design before coding. The skill clarifies goals and constraints through focused questions, compares possible approaches, and produces a reviewed specification ready for implementation planning.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code changes from a chosen Git reference against both project coding standards and the original requirements. Separate agents examine each perspective in parallel, and the results stay separate so specification gaps and coding issues are visible.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Start or resume a development workflow by checking the request and current change state. Routes work through proposal, design, implementation, verification, and archiving, with separate paths for bug fixes and smaller changes and pauses for required user decisions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide a development change through requirements, design, implementation, verification, and archiving. Comet combines OpenSpec for specifications with Superpowers for technical work, detects the current phase, and routes the agent to the appropriate next step.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Routes a Comet request to the Native or Classic workflow based on project settings. When project settings are missing, it saves the global defaults locally so later changes to those defaults do not alter the project's choice.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Start a Comet task without choosing Native or Classic yourself. This entry skill reads the project’s workflow configuration, activates the configured option, and forwards the original request unchanged to the matching skill so work follows the project’s saved settings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.