Skip to main content
command CX Codex

reflect · superclaude-org — Claude Code command: what it does, how to install

reflect evaluates task adherence and session progress using Serena MCP analysis tools. Useful for quality checks before marking tasks as complete.

MIT ★ 23,950 updated 2026-09-27

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/reflect.md
Open on GitHub

What reflect does

The /sc:reflect command inspects task progress, checks requirement fulfillment, and tracks session metadata. It connects TodoRead and TodoWrite task patterns directly to Serena reflection tools, such as think_about_task_adherence for catching deviations and think_about_whether_you_are_done for verifying completion criteria.

For retaining context across work sessions, it executes read_memory and write_memory calls. The core reflection process is built to finish in under 200ms, while checkpoint creation takes less than 1s.

Serena MCP is mandatory here: the command will fail to run if those reflection tools are missing.

What it helps with

  • validate task adherence against initial project goals
  • verify completion criteria before closing a session
  • persist learned insights across sessions using Serena memory
  • detect blockers and work deviations during execution

Example prompts for the agent

  • /sc:reflect --type task --analyze
  • /sc:reflect --type session --validate
  • /sc:reflect --type completion

How to install reflect

Manually: put the files in place

.claude/commands/reflect.md

Call it with /reflect. For all projects use ~/.claude/commands/

Questions about reflect

How to install reflect in Claude Code?

Add the command definition file to .claude/commands/reflect.md.

What does the reflect command do?

It runs reflection and quality checks against active tasks, verifying whether work meets requirements before wrapping up.

Does reflect require Serena MCP?

Yes, Serena MCP is required because the command relies directly on its reflection and memory tools.

Source text

reflect.md · MIT
---
name: reflect
description: "Task reflection and validation using Serena MCP analysis capabilities"
category: special
complexity: standard
mcp-servers: [serena]
personas: []
---

# /sc:reflect - Task Reflection and Validation

## Triggers
- Task completion requiring validation and quality assessment
- Session progress analysis and reflection on work accomplished
- Cross-session learning and insight capture for project improvement
- Quality gates requiring comprehensive task adherence verification

## Usage
```
/sc:reflect [--type task|session|completion] [--analyze] [--validate]
```

## Behavioral Flow
1. **Analyze**: Examine current task state and session progress using Serena reflection tools
2. **Validate**: Assess task adherence, completion quality, and requirement fulfillment
3. **Reflect**: Apply deep analysis of collected information and session insights
4. **Document**: Update session metadata and capture learning insights
5. **Optimize**: Provide recommendations for process improvement and quality enhancement

Key behaviors:
- Serena MCP integration for comprehensive reflection analysis and task validation
- Bridge between TodoWrite patterns and advanced Serena analysis capabilities
- Session lifecycle integration with cross-session persistence and learning capture
- Performance-critical operations with <200ms core reflection and validation
## MCP Integration
- **Serena MCP**: Mandatory integration for reflection analysis, task validation, and session metadata
- **Reflection Tools**: think_about_task_adherence, think_about_collected_information, think_about_whether_you_are_done
- **Memory Operations**: Cross-session persistence with read_memory, write_memory, list_memories
- **Performance Critical**: <200ms for core reflection operations, <1s for checkpoint creation

## Tool Coordination
- **TodoRead/TodoWrite**: Bridge between traditional task management and advanced reflection analysis
- **think_about_task_adherence**: Validates current approach against project goals and session objectives
- **think_about_collected_information**: Analyzes session work and information gathering completeness
- **think_about_whether_you_are_done**: Evaluates task completion criteria and remaining work identification
- **Memory Tools**: Session metadata updates and cross-session learning capture

## Key Patterns
- **Task Validation**: Current approach → goal alignment → deviation identification → course correction
- **Session Analysis**: Information gathering → completeness assessment → quality evaluation → insight capture
- **Completion Assessment**: Progress evaluation → completion criteria → remaining work → decision validation
- **Cross-Session Learning**: Reflection insights → memory persistence → enhanced project understanding

## Examples

### Task Adherence Reflection
```
/sc:reflect --type task --analyze
# Validates current approach against project goals
# Identifies deviations and provides course correction recommendations
```

### Session Progress Analysis
```
/sc:reflect --type session --validate
# Comprehensive analysis of session work and information gathering
# Quality assessment and gap identification for project improvement
```

### Completion Validation
```
/sc:reflect --type completion
# Evaluates task completion criteria against actual progress
# Determines readiness for task completion and identifies remaining blockers
```

## Boundaries

**Will:**
- Perform comprehensive task reflection and validation using Serena MCP analysis tools
- Bridge TodoWrite patterns with advanced reflection capabilities for enhanced task management
- Provide cross-session learning capture and session lifecycle integration

**Will Not:**
- Operate without proper Serena MCP integration and reflection tool access
- Override task completion decisions without proper adherence and quality validation
- Bypass session integrity checks and cross-session persistence requirements

© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

reflect by other authors comes first.

reflect ccplugins The reflect command gathers session corrections and proposes changes to CLAUDE.md for human review. It can also inspect sync targets and spot similar entries. CX Codex +1 ★ 1,013repo stars reflect John Rogers (@johnrogers) reflect is a Claude Code command that reviews chat context and project settings, then suggests changes to instructions, commands, and configuration. CX Codex +1 ★ 233repo stars memory-reflect basicmachines-co memory-reflect is a Claude Code skill that reviews recent project logs and merges durable decisions into persistent notes. It runs on a scheduled heartbeat or on request. CX Codex +1 1,500installs claude-self-reflect ramakay claude-self-reflect stores Claude Code conversation history locally and retrieves past context with sub-millisecond vector search. Keeps your decisions and task state across multiple sessions. ★ 231repo stars personal-assistant ailabs-393 Turns your agent into a personal assistant that keeps a profile, tasks, schedule and habits, and tailors answers to your preferences. CX Codex +1 2,700installs groove andreadellacorte This skill turns plain-language requests into workflow commands. Use it for planning, task tracking, memory logs, and Groove administration. CX Codex +1 633installs CLEO MCP Server kryptobaseddev CLEO MCP Server orchestrates AI coding agents with hierarchical task tracking, long-term memory, and session continuity across editor restarts. CX Codex +1 ★ 159repo stars Agendum sralli Agendum provides persistent memory for AI agents, converts plans into task graphs, and scopes context across coding sessions. CX Codex +1 ★ 6repo stars

From the same set56

The whole set →
save save preserves session context, discoveries, and recovery points through Serena MCP. Use it when work needs to continue across sessions. CX Codex +1 ★ 23,950repo stars select-tool select-tool is a Claude Code command that routes operations to Serena or Morphllm based on complexity, balancing accuracy and speed. CX Codex +1 ★ 23,950repo stars business-panel business-panel runs document analysis through a panel of simulated business thinkers to deliver structured strategic synthesis. CX Codex +1 ★ 23,950repo stars research research — a command for investigating complex questions beyond your knowledge cutoff. It breaks down the task automatically, runs parallel searches, and collects evidence with source attribution. CX Codex +1 ★ 23,950repo stars explain A command to explain code, system architecture, and concepts at the right level of depth. Helps you understand unfamiliar code or teach concepts to others. CX Codex +1 ★ 23,950repo stars index index scans project architecture to build structured knowledge bases, API references, or README files with cross-references. CX Codex +1 ★ 23,950repo stars troubleshoot troubleshoot diagnoses runtime errors, build failures, performance bottlenecks, and deployment bugs. It inspects the system state and never modifies files unless passed --fix. CX Codex +1 ★ 23,950repo stars spawn spawn — a command that breaks down large multi-domain operations into hierarchical task plans with dependencies and delegation. Analyzes scope, decomposes work, and assigns executors—it plans rather than implements. CX Codex +1 ★ 23,950repo stars

Project sponsors

Companies that keep this analytics open