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

grilling

Shared interview engine for /brainstorm, /prd, and grill-me. Asks only the open frontier of a question set, looks up facts instead of asking them, and returns a question count. Engine only; not invoked on its own.

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

indigoai-us/hq-coreスター 90(GitHub 90 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(3)

  • SKILL.md4.7 KB
  • agents/openai.yaml131 B
  • frontier.sh4.6 KB

SKILL.md(原文)

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

Grilling Engine

Engine skill. Caller skills (/brainstorm, /prd, grill-me) load this file and run it with an input contract. Users do not run it directly. If a user types /grilling, tell them to use /brainstorm, /prd, or grill-me instead.

Pattern source: mattpocock/skills skills/productivity/grilling (design tree, frontier rounds, facts are the agent's job). HQ changes the default: one question per AskUserQuestion call, with rounds available only on request.

Input contract

InputRequiredMeaning
question_setyesPath to a question-set file. Format: .claude/skills/_shared/questions/FORMAT.md.
known_factsnoMap of question id to answer, already settled by the caller (from the brief, a brainstorm, the board, or earlier answers). These ids are never asked.
modenoone-at-a-time (default) or rounds.
max_questionsnoUpper bound on questions put to the user. Default: no limit. When reached, remaining decisions take their recommended option and are logged as assumed.

mode: rounds is set only when the user explicitly asks for rounds in this session or the caller received a --rounds argument. Never infer it from the size of the set, the user's tone, or time pressure.

Helper

.claude/skills/grilling/frontier.sh parses the set and computes the frontier. Use it rather than computing dependencies by hand.

bash .claude/skills/grilling/frontier.sh frontier <question_set> --known <ids> --answered <ids>
bash .claude/skills/grilling/frontier.sh count <question_set> --known <ids>

frontier prints the open decision ids in file order. count validates the set and prints the count object for a full run. Exit 2 means the set is malformed or has a dependency cycle; stop and report the error to the caller.

Procedure

  1. Validate. Run frontier.sh count with the known ids. On exit 2, return the error to the caller without asking anything.

  2. Resolve facts. For every kind: fact question whose depends_on are resolved, find the answer yourself: caller research, the company board, repo files, or a Task subagent lookup. Never put a fact question to the user. A pending lookup blocks only the questions that depend on it; keep asking the rest of the frontier.

  3. Compute the frontier. Run frontier.sh frontier with known ids plus everything answered so far. A question whose dependency is still open waits for a later pass.

  4. Ask.

    • one-at-a-time (default): one AskUserQuestion call per frontier question. Offer 2 to 4 options from the question's options. When research or known facts support the recommended option, put it first and append (Recommended) to its label. Wait for the answer before the next call.

    • rounds: present the whole frontier as one numbered block, then wait for the reply.

      Q1 - <question text>
      Options: A) <opt> B) <opt> C) <opt>
      Recommended: A) <opt>
      
      Q2 - ...
      

      Word each question so "yes" accepts the recommendation. Accept shorthand replies: yes or y (accept all recommendations), 1A 2C, 2: <free text>, or all recommended except 3B. Questions not mentioned in a reply take the recommendation only when the reply was yes; otherwise ask about them again in the next round.

  5. Record. After each answer, append it to the active journal:

    bash .claude/skills/_shared/journal.sh append <project_dir> decisions "<question id>: <answer>"
    

    Facts found in step 2 go under findings with their id and source.

  6. Repeat steps 2 to 5 until the frontier is empty or max_questions is reached.

  7. Return the answers map and the count object to the caller.

Headless

When CLAUDE_HEADLESS=1, do not call AskUserQuestion. Take the recommended option for each decision, log it under decisions with the suffix (assumed, headless), and count it under asked.

Count object

{"asked": 7, "skipped_known": 3, "skipped_fact": 2,
 "by_tier": {"strategic": 1, "architecture": 3, "quality": 3}}
  • asked: decisions put to the user (or assumed under headless or max_questions).
  • skipped_known: ids supplied in known_facts.
  • skipped_fact: fact questions resolved by lookup.
  • by_tier: asked split by tier.

Test: bash core/scripts/tests/grilling-count.test.sh.

レビュー

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

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

accept

無料

Accept HQ membership invites from a magic link or raw token.

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

indigoai-us/hq-core902026年10月26日 更新

adr

無料

Capture qualifying architecture decisions as ADRs in the right HQ or repo location.

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

indigoai-us/hq-core902026年10月26日 更新

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

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

indigoai-us/hq-core902026年10月26日 更新

architect

無料

Find shallow modules and propose deepening refactors, ranked with file refs; never edits code. Use when code is hard to change or planning a refactor.

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

indigoai-us/hq-core902026年10月26日 更新

Generate dark ASCII banner graphics for HQ and social launch assets.

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

indigoai-us/hq-core902026年10月26日 更新

Compare approaches to best-in-class prior art, merge existing work, verify cruft removal, and recommend the most durable design before PRD work.

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

indigoai-us/hq-core902026年10月26日 更新

indigoai-us のスキルをすべて見る

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