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

reflection

Automatic quality check on significant outputs via isolated sub-agent. Spawns reflection-agent for objective evaluation without conversation context bias.

インストール方法を見る

含まれるファイル(10)

  • SKILL.md4.8 KB
  • criteria/phase-0-discovery.yaml2.5 KB
  • criteria/phase-1-prd.yaml2.5 KB
  • criteria/phase-2-tech-spec.yaml2.6 KB
  • criteria/phase-3-impl-plan.yaml9.0 KB
  • criteria/phase-4-development.yaml3.4 KB
  • criteria/phase-4a-code-design.yaml3.9 KB
  • criteria/phase-4b-code-function.yaml5.0 KB
  • criteria/phase-5-qa-ship.yaml3.7 KB
  • SKILL.extended.md13.1 KB

SKILL.md(原文)

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

Reflection Skill

Apply (spawn agent): code, architecture, PRD, specs, tests, plans, APIs, schemas. Skip: simple questions, status checks, file reading, clarifying questions, help.

The sub-agent gets NO conversation context. It evaluates purely on merit — inline evaluation shares your context, agrees with your reasoning, and trends to 10/10. The agent sees only output + request + WHY, and can verify claims in source files.

Process

  1. Extract isolation variables (below).
  2. Spawn reflection-agent with isolated inputs.
  3. Parse JSON response.
  4. If pass=false and revisions<3: apply guidance, re-evaluate.
  5. Display Quality Check box.

Context Extraction (CRITICAL)

Extract these for the agent. Do NOT summarize or add context.

VariableHow to Extract
{{ORIGINAL_REQUEST}}First user message that initiated this task - VERBATIM
{{STATED_WHY}}The WHY established at conversation start - EXACT TEXT
{{PHASE_NUMBER}}Read from .aid/state.json → current_phase
{{PHASE_NAME}}Read from .aid/state.json → phase_name
{{OUTPUT_TO_EVALUATE}}Your draft output (code, spec, etc.)
{{FILES_TO_VERIFY}}Read content of all files your output references/modifies
{{PHASE_CRITERIA}}Read from criteria/phase-{N}-{name}.yaml

DO: copy original request exactly as user wrote it; copy stated WHY exactly as established; include ALL files the output references (not just some); load criteria from the YAML file.

DO NOT: ❌ summarize the request; ❌ explain your decisions; ❌ include conversation history; ❌ mention previous attempts; ❌ add "helpful context".

Spawn Command

Task(
  subagent_type: "general-purpose",
  model: "opus",
  prompt: [Load ../../agents/reflection-agent.md, replace variables],
  description: "Objective quality evaluation"
)

Quality Check Display Format

After receiving agent response, display:

╭─────────────────────────────────────────────────────────────╮
│ 🔍 Quality Check                                            │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  [icon] WHY Alignment     X/10   [agent's note]             │
│  [icon] Phase Compliance  X/10   [agent's note]             │
│  [icon] Correctness       X/10   [agent's note]             │
│  [icon] Security          X/10   [agent's note]             │
│  [icon] Completeness      X/10   [agent's note]             │
│                                                             │
│  ══════════════════════════════════════════════════════     │
│  📊 Overall: X.X/10                                         │
│  STATUS: [agent's status]                                   │
│                                                             │
│  [If revised: 📝 Improvements: ...]                         │
│                                                             │
╰─────────────────────────────────────────────────────────────╯

Score Icons

ScoreIcon
8-10✅
6-7.9⚠️
0-5.9❌

Revision Handling

If agent returns pass: false:

  1. Read revision_guidance.required_changes
  2. Apply changes to your output
  3. Re-spawn agent with updated output (max 3 attempts)
  4. Track improvements: "Security 5→8/10 Fixed: Added input validation"

Session Review Mode

On project load or /good-morning, spawn session review instead:

Task(
  subagent_type: "general-purpose",
  model: "opus",
  prompt: [Load ../../agents/reflection-agent.md],
  description: "Session review - outside perspective"
)

Session review variables:

  • {{STATE_JSON}} - Content of .aid/state.json
  • {{CONTEXT_JSON}} - Content of .aid/context.json
  • {{RECENT_CHANGES}} - Output of git log --oneline -10
  • {{RECENT_FILES}} - Output of git diff --stat HEAD~5
  • {{PHASE_CRITERIA}} - Current phase criteria YAML

Commands

CommandAction
/reflectShow detailed breakdown of last evaluation
/reflect --sessionRun session review
/reflect --strictRun evaluation with threshold 8.0

レビュー

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

同じリポジトリのスキル

概要と使いどころ

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

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

ilandahan/AID102026年9月23日 更新

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

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

ilandahan/AID102026年9月23日 更新

AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.

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

ilandahan/AID102026年9月23日 更新

aid-prd

無料

AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.

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

ilandahan/AID102026年9月23日 更新

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

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

ilandahan/AID102026年9月23日 更新

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.

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

ilandahan/AID102026年9月23日 更新

ilandahan のスキルをすべて見る

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