reflection

Analyze conversation context and repository state to propose phased ecosystem improvements.

17|1|Updated Nov 17, 2024
One-click install
npx skills add https://github.com/mifunedev/orchestra --skill reflection-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflection
Source: https://github.com/mifunedev/orchestra/tree/main/.claude/skills/reflection
Command: npx skills add https://github.com/mifunedev/orchestra --skill reflection-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables safe, meta-level analysis and orchestration of the AI agent ecosystem by supervising and coordinating improvements to agents, skills, and commands.

Core Features & Use Cases

  • Supervisor-first analysis and Phase-based workflow
  • Builder-agent coordination with explicit user approvals
  • Dependency-aware sequencing (Agents → Skills → Commands)
  • Documentation sync to CLAUDE.md after changes

Quick Start

Start by invoking reflection to generate an initial supervisor report and await approval before any changes.

Frequently Asked Questions about reflection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely orchestrate improvements to my AI agent ecosystem?

You orchestrate AI agent ecosystem improvements safely by using a supervisor-first analysis to generate phased builder workflows that require explicit user approvals before modifying agents, skills, or commands.

How do I automate dependency-aware sequencing when updating agents and skills?

Dependency-aware sequencing for updates is automated by assessing repository state and conversation history, then structuring the workflow to modify Agents first, followed by Skills, then Commands. This ensures foundational dependencies are resolved before downstream components change.

Can I sync AI agent workflow changes to my CLAUDE.md documentation automatically?

Yes, AI agent workflow changes can be synced to CLAUDE.md documentation automatically as part of the structured proposal output. The supervision process includes documentation updates to ensure the repository's CLAUDE structure reflects the applied meta-improvements.

What's the best way to supervise meta-improvements for AI agent workflows?

The best way to supervise meta-improvements for AI agent workflows is to analyze the existing conversation context, git status, and CLAUDE structure to generate structured proposals. This allows you to review and approve builder-agent coordinated phases before execution.

Do I need git status access to analyze and propose meta-improvements for my repository?

Yes, git status access is required to analyze and propose meta-improvements accurately. The supervision process relies on repository state alongside conversation history and the CLAUDE structure to generate safe, context-aware proposals for your AI agent ecosystem.

When should I not use a supervisor-first workflow for modifying agent commands?

A supervisor-first workflow for modifying agent commands may not suit rapid, isolated changes that do not impact the broader ecosystem dependency chain. It is designed for comprehensive meta-level coordination rather than simple, independent command updates.