Design, review, and debug agent workflows, and decide when a request should use a prompt, instruction, skill, agent, or hook before escalating to multi-agent design. Use for .agent.md / .instructions.md / .prompt.md / AGENTS.md work, workflow architecture, orchestration planning, scheduled automation model allocation, or when agent workflows may be overkill. Triggers on 'agent workflow', 'create agent', 'automation models', 'ワークフロー設計', 'orchestrator'.
goal-loop
Run an explicit end-to-end goal loop with frozen Scope/criteria, worker delegation, external verification, evaluator review, and bounded retries. Use when the user asks for 'goal-loop', 'ゴールまで回す', '必ずやり遂げる', 'loop until done', 'until it actually works', or an orchestrator + evaluator loop. Do not use for ordinary planning, casual advice, reviews, or small single-file fixes.
含まれるファイル(8)
- SKILL.md5.7 KB
- LICENSE.txt5.2 KB
- references/criteria-agreement.md6.2 KB
- references/design-rationale.md2.0 KB
- references/evaluation-rubric.md5.0 KB
- references/ledger-templates.md8.2 KB
- references/loop-control.md12.6 KB
- references/steering-and-final-gates.md8.9 KB
SKILL.md(原文)
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Goal Loop
合意した Scope と success criteria を満たすまで、worker / verifier / evaluator を使ってゴールをやり遂げる手順書。 このスキルを起動した現在の agent が orchestrator になり、criteria、ledger、evidence reconciliation、次の一手の決定を担う。
When to Use
- ユーザーが
goal-loop/ゴールまで回す/必ずやり遂げる/loop until done/until it actually worksと依頼した。 - 成果物を end-to-end に完成させる必要があり、単発修正ではなく検証・再試行・評価のループが必要。
- worker 生成と evaluator 判定を分ける価値がある、中規模以上または不可逆・多段の作業。
Do Not Use For
- 1 ファイル・自明・低リスクの修正。通常 agent が直接実行する。
- 普通の相談、計画だけ、コードレビューだけ、事実確認だけ。
- skill / prompt / instruction / agent 自体の設計レビュー。この skill の対象外。
Execution Contract
- Freeze scope, AC, verifier, out-of-scope, must NOT, autonomy, and persistence before execution.
- Keep a compact ledger: AC status, evidence, attempts, gaps, and next action.
- Delegate broad research, mutation, and primary verification when workers are available; workers return evidence only.
- Before parallel durable dispatch, checkpoint each partition identity, expected evidence, and wait deadline. After cancellation, retry, or a missing parent completion, reconcile durable evidence first and rerun only unresolved partitions.
- Judge by external signals first. Never PASS from self-evaluation, supporting checks alone, skipped tests, TODOs, or weakened criteria.
- On failure, update the ledger from the failed signal, change approach, and avoid repeating attempts.
- Use Small-Bet-First for broad, irreversible, dependency, schema, deployment, or user-facing changes.
- Stop or replan on stall, oscillation, diminishing returns, budget exhaustion, or genuine external blockers.
Phase 1: Scope + Criteria Freeze
- Freeze goal, scope terminus, AC with
verify:, primary verifier, out-of-scope, must NOT, autonomy, and persistence. - If the finish line is ambiguous, ask one structured question before execution.
- Do not use build/control-plane success as the primary verifier when the real outcome is deploy / runtime / UI / app behavior.
Phase 2: Plan Minimal Subgoals
Use steering-and-final-gates.md and ledger-templates.md.
- Pick the lightest effort level that still protects the goal; downgrade trivial work.
- Split into verifiable subgoals and record status. Parallelize read-only work, or independently partitioned mutations with durable identity, idempotency, expected evidence, and conflict-free ownership.
Phase 3: Delegate Workers
Use loop-control.md.
- Start broad or risky changes with a pilot; never expand a failed pilot.
- Give workers only the subgoal, AC, boundaries, must NOT, relevant attempt lessons, and expected evidence.
- Treat parent tool receipt, UI state, and
turn_endas delivery evidence, not completion authority; use terminal child state plus verified durable artifacts. - If no subagent tool exists, record degraded mode; only downgraded small work may run in main context.
Phase 4: External Verification
- Run the frozen
verify:steps and capture exit codes, logs, screenshots, readbacks, or capability gaps. - If the primary verifier is unavailable, record exact manual verification steps and required evidence; do not complete from weaker checks.
Phase 5: Evaluate
Use evaluation-rubric.md.
- Reconcile evidence against each AC. Use a separate evaluator for non-small or non-read-only work.
- PASS only when every must AC passes and confidence is above threshold.
Phase 6: Loop Control
Use loop-control.md.
- If unmet, update the ledger from the external signal and replan before adding workers.
- Escalate only after the Blocker Test proves the blocker is external or structural.
Phase 7: Report or Handoff
- Report AC-by-AC status, primary evidence, supporting checks, capability gaps, criteria changes, and residual risks.
- For high-risk changes, include final quality gate and independent review evidence.
- Cleanup scratch state unless it is needed for resumability.
References
- criteria-agreement.md: Scope / criteria freeze テンプレ。
- ledger-templates.md: Task / Progress ledger と attempt table。
- loop-control.md: stop、replan、Small-Bet、reflection、HITL。
- evaluation-rubric.md: rubric と judge bias 対策。
- steering-and-final-gates.md: Effort Scaling、dynamic steering、final gate、worker boundary。
- design-rationale.md: 設計根拠と出典。
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Design, run, and review fair performance, token, and cost comparisons across GitHub Copilot CLI, Codex CLI, and direct model APIs. Use for AI CLI benchmark, Copilot vs Codex, prompt-cache diagnosis, cache read/write analysis, fresh-process latency measurement, token-cost comparison, or when a benchmark must separate provider caching from local CLI caches.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze historical VS Code GitHub Copilot Chat sessions by model, reasoning effort, AIU, time, reliability, workflow behavior, and external quality evidence, or safely prune workspace-scoped local chat history by age. Use for session analysis, repeated-task retrospectives, model evaluation, cost/performance analysis, and old session cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Create reproducible animated infographic GIFs from structured data or measured results, with audience-language labels, explicit timing semantics, representative-frame QA, and a static fallback. Use when asked for GIF生成, animated infographic, 動的インフォグラフィック, 結果が流れる図, animated benchmark, or a blog/SNS animation whose displayed metrics must remain traceable to source data.
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid. Also use for Archify, interactive or animated HTML diagrams, インタラクティブ図, 動く構成図. When an editable .drawio file is required, use the draw.io workflow instead and treat Archify HTML only as a supplement.
Generate ASCII-art text banners for terminals, READMEs, and CLI startup messages. Use when a user asks for an ASCII banner, text art, バナー, アスキーアート, or a decorative header for a script/README.