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

deepen

Make a task deeper, not bigger. Use when the user asks for a deeper or more ambitious version of a task (tiefer, geh tiefer, go deeper, ambitionierter, wie würde ein Profi das angehen) or hands over an outcome-shaped deliverable (Bericht, Auswertung, Analyse, Plan, Audit, Deck, Performance-Ziel) with no ceiling word, or types /deepen [task]. Not for single-step edits, short commands (run the tests, commit), bug fixes, prompt-wording rewrites, or any request carrying nur, bloß, schnell, just, only, quick.

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

Kanevry/session-orchestratorスター 52(GitHub 52 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.9 KB

SKILL.md(原文)

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

deepen

Same scope, better work: rawer inputs, sharper methods, a judge that is not the author. Never more deliverables.

Invocation

Invoked as /deepen [task] with arguments: $ARGUMENTS, or by the model when the description matches. The task is $ARGUMENTS; if that is empty, the task is the operator's last request in this conversation. If there is none, say so and stop.

Stage 1 — Intake

Quote the request verbatim. Then decide:

  • Bypass when any of these holds:

    • a ceiling word: nur, bloß (bloss), schnell, just, only, quick;
    • a single-step edit (rename, one-line change, typo);
    • a short command (run the tests, commit, push, build);
    • a bug fix;
    • a request to reword a prompt or text;
    • the request arrived as a coordinator brief, or you run as a dispatched subagent: your scope was set upstream, so do the task and note a deeper version in one line.

    Print exactly one line Ambition check: bypassed (<reason>) and do the task as asked. Nothing else from this skill: no questions, no rewrite, no extra work (a dispatched agent adds only its one-line note).

  • Expand otherwise. Print Ambition check: expanding (<reason>) and go to Stage 2.

Stage 2 — Deepen

Answer the four questions of skills/plan/prd-premortem-panel.md § Brief B (Practice, Raw material, Methods and tools, Oracle) for this task, not for a PRD. Work them against the real material: open the files, list the directories, run cheap read-only commands. Never answer from memory what one ls would show. Pick the oracle per § Judge order in the same file.

Then emit this block:

### Ambition Rewrite
- Original request: <verbatim>
- Raw inputs to read: <files, data, logs, history, as found in Stage 2>
- Methods and instruments: <specific methods and tools>
- Target: <the operator's target, unchanged, is the bar>; stretch: <a harder number, if any>
  (no target given: proposed: <one checkable target>)
- Outside judge: <exact command, test, query or reviewer per § Judge order> | none available
- Out of scope / follow-ups: <everything that would make the task bigger>
- Cost and side effects: <time, tokens, money, writes, external effects>

Stage 3 — Stop

Execute nothing yet. Ask the operator:

  • Interactive session: AskUserQuestion, header Deepen, 2–3 options, recommendation first, each with reason, cost and consequence: run the rewrite (Recommended) / run the original as asked / narrow the rewrite.
  • No AskUserQuestion (lead-led session, headless run, tool unavailable): end the turn with the block and wait for the instruction.

Stage 4 — Execute and judge

Run what the operator chose. Then run the outside judge and paste its output unedited. If it fails, fix the work and rerun, at most three rounds; then report the remaining failure as it stands.

  • Never edit the judge (test, query, threshold, rubric) to make it pass.
  • No judge exists: the result line is UNVERIFIED: kein Außenrichter (<what would provide one>). Carry it into the session summary section ### Unverified (kein Außenrichter).

Never

  • Add deliverables, audiences or systems. Bigger goes to Out of scope / follow-ups.
  • Expand a request that carries a ceiling word.
  • Speak in a persona voice.
  • Dispatch subagents unless the operator agreed to it.

Method after Felix Rieseberg, "How to be more ambitious" (13 October 2026).

レビュー

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

コメント

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

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

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

0 / 1000 文字

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

同じリポジトリのスキル

Use when the user asks to improve architecture, find refactoring opportunities, surface deepening opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable. Surfaces shallow modules and hypothetical seams using a precise vocabulary (Module / Interface / Implementation / Depth / Seam / Adapter / Leverage / Locality from LANGUAGE.md).

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

Kanevry/session-orchestrator522026年10月29日 更新

autopilot

無料

Use this skill when running an autonomous session-orchestration loop. Chains session-start → session-plan → wave-executor → session-end for N iterations with all 10 kill-switches (SPIRAL, FAILED wave, carryover > 50%, max-hours, max-sessions, resource-overload, token-budget, stall-timeout, sub-threshold confidence, user-abort). Reads Mode-Selector output (Phase B) to decide auto-execute vs. fallback. Writes one autopilot.jsonl record per loop run. Phase C scaffold (issue #277); implementation lives in scripts/lib/autopilot.mjs (Phase C-1 follow-up).

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

Kanevry/session-orchestrator522026年10月29日 更新

bootstrap

無料

Use this skill when scaffolding the minimum repository structure required by session-orchestrator. Invoked automatically by the Bootstrap Gate when CLAUDE.md, Session Config, or bootstrap.lock is missing. Also available as /bootstrap for manual invocation. Three intensity tiers: fast (demos/spikes), standard (MVPs), deep (production/team).

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

Kanevry/session-orchestrator522026年10月29日 更新

Use when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue (3-5 AUQ rounds) and writes a spec markdown file. Use BEFORE /plan feature when product intent needs validation; skip to /plan feature when scope is already clear. HARD-GATE prevents any code work until the design is user-approved.

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

Kanevry/session-orchestrator522026年10月29日 更新

Use when detecting drift between CLAUDE.md (or AGENTS.md, the Codex CLI alias) / _meta narrative and live repository state. Ten checks: absolute-path resolution, 01-projects/ count claims, issue-reference freshness, session-file existence, command-count sync, session-config-parity (mandatory template keys = error, opt-in gaps = note, unknown local keys = warning), vault-dir-parity (CLAUDE.md vs AGENTS.md), generated-rule-staleness (WARN-only), rule-scoping (paths:/globs: frontmatter defects, dangling rule citations, zero-match globs), and docs-parity (docs/components.md count-claims vs on-disk counts, template-vs-reference config-key parity, stale .claude/metrics/ paths). Full per-check spec in the body table. Invoked as an opt-in session-end phase; mirrors vault-sync's lean JSON+exit-code contract.

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

Kanevry/session-orchestrator522026年10月29日 更新

close

無料

End session with verification, commits, and documentation

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

Kanevry/session-orchestrator522026年10月29日 更新

Kanevry のスキルをすべて見る

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