evolving-status
npx machina-cli add skill claude-world/director-mode-lite/evolving-status --openclawFiles (1)
SKILL.md
1.7 KB
Self-Evolving Loop Status
View status, history, and memory metrics for evolving-loop sessions.
Usage
# 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
Output Example
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
Views
| 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 |
Related
- /evolving-loop - Main development loop
- Architecture - Detailed design
Source
git clone https://github.com/claude-world/director-mode-lite/blob/main/skills/evolving-status/SKILL.mdView on GitHub Overview
Evolving-status provides a snapshot of the current Self-Evolving Loop session, including status, history, and memory metrics. It supports detailed JSON state, reports, and views into evolution and dependencies to aid debugging and optimization.
How This Skill Works
Invoke /evolving-status to fetch the current session state. Use --detailed for a full JSON view, and --report <type> to pull a focused report (analysis, validation, decision, learning, or patterns). Additional flags (--history, --evolution, --memory, --dependencies) expose historical events, version history, memory metrics, and tool dependencies.
When to Use It
- You need the current status of an evolving-loop session (status, phase, iteration, started time).
- You want a specific report (analysis, validation, decision, learning, patterns) to diagnose a bottleneck or outcome.
- You need to review recent event history to trace changes across iterations.
- You want to inspect how the skill has evolved over time (version history) or understand memory usage.
- You need to understand tool dependencies and how co-usage affects the evolving loop.
Quick Start
- Step 1: Run /evolving-status to fetch the current session state.
- Step 2: If needed, run /evolving-status --detailed for full JSON or /evolving-status --report <type> for a focused view.
- Step 3: Use --history, --evolution, or --memory to drill into history, evolution, or memory metrics.
Best Practices
- Start with /evolving-status for a quick pulse check, then switch to --detailed for a full JSON state during debugging.
- Use --report with a specific type to narrow focus on the most relevant aspect of the loop.
- Regularly review --history to detect drift or regressions in behavior across iterations.
- Monitor --memory to identify leaks or memory pressure in long-running sessions.
- Cross-reference --evolution and --dependencies to correlate changes with performance or outcomes.
Example Use Cases
- /evolving-status
- /evolving-status --report analysis
- /evolving-status --history
- /evolving-status --evolution
- /evolving-status --memory
Frequently Asked Questions
Add this skill to your agents
