changelog-observer
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
View Self-Evolving Loop session status, history, and memory metrics
$ npx -y skills add claude-world/director-mode-lite --skill evolving-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/evolving-statusContext preview
The summary Claude sees to decide when to auto-load this skill.
View Self-Evolving Loop session status, history, and memory metrics
name: evolving-status description: View Self-Evolving Loop session status, history, and memory metrics user-invocable: true
View status, history, and memory metrics for evolving-loop sessions.
---
# Current session status /evolving-status # Detailed view /evolving-status --detailed # View specific report /evolving-status --report analysis /evolving-status --report validation /evolving-status --report decision /evolving-status --report learning /evolving-status --report patterns # View event history /evolving-status --history # View skill evolution /evolving-status --evolution # View memory system /evolving-status --memory # View tool dependencies /evolving-status --dependencies
---
Status: in_progress Phase: EXECUTE Iteration: 3 / 50 Started: 2026-01-14T12:00:00Z Request: Build REST API with user authentication... Skill Versions: executor: v2 validator: v1 fixer: v1 Lifecycle Status: executor: task-scoped validator: task-scoped fixer: task-scoped Task Type: auth (pattern: auth) Acceptance Criteria: [x] AC-F1: GET /users endpoint [x] AC-F2: POST /users endpoint [ ] AC-F3: Input validation
---
| Flag | Description | |------|-------------| | `--detailed` | Full JSON state | | `--report <type>` | View specific report | | `--history` | Last 20 events | | `--evolution` | Skill version history | | `--memory` | Memory system metrics | | `--dependencies` | Tool co-usage graph |
---
Use Claude Code like a Director, not a Programmer. MIT toolkit with Auto-Loop, guided setup, 27 commands, 14 agents, and 32 skills.
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.
TDD-based autonomous development loop with checkpoint recovery and observability changelog