home / skills / oimiragieo / agent-studio / recommend-evolution

recommend-evolution skill

/.claude/skills/recommend-evolution

This skill detects capability gaps and records standardized evolution recommendations to guide planning across reflection, routing, and integration contexts.

npx playbooks add skill oimiragieo/agent-studio --skill recommend-evolution

Review the files below or copy the command above to add this skill to your agents.

Files (11)
SKILL.md
3.8 KB
---
name: recommend-evolution
description: Detect capability gaps and record standardized evolution recommendations.
version: 1.0.0
model: sonnet
invoked_by: both
user_invocable: true
tools: [Read, Write, Edit, Skill]
error_handling: graceful
streaming: supported
---

# Recommend Evolution

## Overview

Recommend ecosystem evolution when repeated evidence indicates missing capability, and record the recommendation in a standard machine-readable format.

## When to Use

- Reflection identifies recurring delivery failures with the same root cause
- Router/analysis signals no suitable agent or skill for recurring requests
- Repeated integration gaps imply missing artifact type or policy
- User explicitly requests a new capability path

## The Iron Law

```
DO NOT SPAWN EVOLUTION-ORCHESTRATOR DIRECTLY FROM THIS SKILL.
RECOMMEND AND RECORD ONLY.
```

<identity>
Evolution recommendation skill for reflection/planning agents.
</identity>

<capabilities>
- Trigger classification (`repeated_error`, `no_agent`, `integration_gap`, `user_request`, `rubric_regression`, `other`)
- Recommendation-vs-integration decision branching
- Dual recording mode: JSONL runtime queue + reflection report block
</capabilities>

<instructions>
<execution_process>

### Step 0: Validate Trigger Type

Use these thresholds:

- `repeated_error`: same class of failure in 5+ tasks
- `rubric_regression`: repeated score drop below threshold for same class of task
- `no_agent`: recurring need with no valid routing match
- `integration_gap`: existing artifact integration missing (prefer artifact-integrator)
- `user_request`: explicit request for capability not available

### Step 1: Decide Recommendation Path

- If gap is integration of existing artifact, prefer:
  `Skill({ skill: 'artifact-integrator' })`
- If gap is stale/underperforming existing skill, prefer:
  `Skill({ skill: 'skill-updater' })`
- If gap requires net-new capability/artifact, continue with evolution recommendation
- If no artifact change needed, update memory only and exit

### Step 2: Create Standard Recommendation Payload

Build one JSON object with required fields:

```json
{
  "timestamp": "2026-02-14T00:00:00.000Z",
  "source": "reflection-agent",
  "trigger": "repeated_error",
  "evidence": "Same routing failure observed in 6 tasks over 2 days.",
  "suggestedArtifactType": "skill",
  "summary": "Create a new routing-context skill for reflection-time grounding.",
  "status": "proposed"
}
```

Schema reference:
`.claude/schemas/evolution-request.schema.json`

### Step 3: Record Recommendation

1. Append JSON line to:
   `.claude/context/runtime/evolution-requests.jsonl`
2. Add required report block:

```markdown
## Evolution Recommendation

- Trigger: <trigger>
- Evidence: <evidence>
- Suggested Artifact Type: <type|null>
- Summary: <1-2 sentences>
- Queue Record: `.claude/context/runtime/evolution-requests.jsonl`
```

### Step 3: Output

Return recommendation summary and what was recorded.

</execution_process>
</instructions>

<examples>
<usage_example>
**Example Invocations**:

```javascript
// Repeated failure pattern -> recommend skill creation
Skill({
  skill: 'recommend-evolution',
  args: '--trigger repeated_error --suggestedArtifactType skill',
});

// Routing miss -> recommend new agent/workflow discussion
Skill({ skill: 'recommend-evolution', args: '--trigger no_agent --suggestedArtifactType agent' });
```

</usage_example>
</examples>

## Memory Protocol (MANDATORY)

**Before starting:**

```powershell
Get-Content .claude/context/memory/learnings.md -TotalCount 120
```

**After completing:**

- Recommendation pattern -> `.claude/context/memory/learnings.md`
- Ambiguous trigger logic -> `.claude/context/memory/issues.md`
- Evolution policy decision -> `.claude/context/memory/decisions.md`

> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Overview

This skill detects repeated capability gaps in an ecosystem and records standardized evolution recommendations for later implementation. It classifies triggers, builds a single machine-readable recommendation payload, and appends that payload to a runtime queue while adding a human-readable report block. It never orchestrates the evolution itself—only recommends and records.

How this skill works

The skill inspects recurring failures, routing misses, integration gaps, rubric regressions, and explicit user requests using defined thresholds (for example, five+ repeated errors). It decides whether to route to integration/updater skills or to prepare a new evolution recommendation. When recommending, it constructs a single JSON object with timestamp, source, trigger, evidence, suggestedArtifactType, summary, and status, writes it to the runtime JSONL queue, and adds a short report block to the reflection output.

When to use it

  • You see the same class of failure across five or more tasks
  • Routing or router analysis shows no valid agent/skill for frequent requests
  • Repeated integration gaps indicate a missing artifact type or connector
  • A rubric or score drops repeatedly for the same task class
  • A user explicitly requests a new capability path

Best practices

  • Validate trigger against thresholds before recommending to avoid noise
  • Prefer artifact-integrator or skill-updater when an existing artifact can solve the gap
  • Keep evidence concise and reproducible (timestamps, counts, example task IDs)
  • Use suggestedArtifactType to guide implementers (agent, skill, artifact, policy)
  • Record both JSONL queue entry and the reflection report block for traceability

Example use cases

  • Reflection agent notices six identical routing failures over three days — recommend a new routing-context skill
  • Router logs show repeated requests with no matching agent — recommend an agent/workflow discussion
  • Integration tests repeatedly fail due to missing file-type handler — recommend an artifact-integrator
  • Product owner requests a feature not supported by any current skill — recommend a new skill and record evidence

FAQ

Will this skill implement the recommended change?

No. It only recommends and records; implementation must be handled by an evolution orchestrator or human team.

Where are recommendations stored?

Recommendations are appended as JSON lines to the runtime queue file and included in a reflection report block for human review.