autonomy

Files (1)

• SKILL.md

SKILL.md (first lines)

# Autonomy Skill

**Invoke automatically** after subagent completion or when deciding next actions.

## When to Invoke (Automatic)

| Trigger | Action |
|---------|--------|
| Subagent returns completed work | Check selected tracking backend for next item |
| Task finishes successfully | Update status, pick next pending item |
| Work pattern detected in user message | Create work items if L2/L3 |
| Multiple tasks identified | Queue all, parallelize if L3 |

## Acceptance Tests

| Test ID | Type | Prompt / Condition | Expected Result |
| --- | --- | --- | --- |
| AUT-T1 | Positive trigger | "Continue with autonomy after this item completes" | skill triggers |
| AUT-T2 | Positive trigger | "Run the next queued item automatically" | skill triggers |
| AUT-T3 | Negative trigger | "Explain what autonomy levels mean" | skill does not auto-dispatch work |
| AUT-T4 | Behavior | no system autonomy level in user ica-config | ask user to set system level (`L1`/`L2`/`L3`), persist choice |
| AUT-T5 | Behavior | no project autonomy level in project ica-config | ask user to set project level (`follow-system`/`L1`/`L2`/`L3`), persist choice |
| AUT-T6 | Behavior | project level is `follow-system` | effective level resolves to system level |
| AUT-T7 | Behavior | project level explicitly set | effective level uses project level override |
| AUT-T8 | Behavior | actionable findings arrive while an item is already `in_progress` | MUST invoke `create-work-items` + `plan-work-items`; `run-work-items` records deferred dispatch and does not preempt |
| AUT-T9 | Behavior | any continuation cycle executes | MUST include all three skills (`create-work-items`, `plan-work-items`, `run-work-items`) with invocation evidence or fail-closed |

## Autonomy Level Configuration (MANDATORY)

Autonomy level MUST be resolved from `ica.config.json` (not tracking config).

Level values:
- `L1`
- `L2`
- `L3`

Project-only value:
- `follow-system`

Required keys:
- System (user) config key: `autonomy.system_level` (`L1` | `L2` | `L3`, default `L2`)
- Project config key: `autonomy.project_level` (`follow-system` | `L1` | `L2` | `L3`, default `follow-system`)

Resolution order:
1. Resolve user (system) config file:
   - `${ICA_HOME}/ica.config.json`
   - `$HOME/.codex/ica.config.json`
   - `$HOME/.claude/ica.config.json`
2. Resolve project config file:
   - `./ica.config.json` (project root)
3. Read `autonomy.system_level` from user config.
4. Read `autonomy.project_level` from project config.
5. Determine effective level:
   - if `autonomy.project_level` is `L1`/`L2`/`L3`, use that
   - if `autonomy.project_level` is `follow-system`, use `autonomy.system_level`

Bootstrap prompts (required if missing):
- If `autonomy.system_level` is missing:
  - ask: "No system autonomy level is configured. Set system autonomy level to `L2` (recommended), `L1`, or `L3`?"
  - persist in user `ica.config.json`
- If `autonomy.project_level` is missing:
  - ask: "No project autonomy level is configured. Set project autonomy level to `follow-system` (recommended), `L1`, `L2`, or `L3`?"
  - persist in project `ica.config.json`

Persistence rules:
- System level MUST be written to user `ica.config.json`.
- Project level MUST be written to project `ica.config.json`.
- If both are missing, ask and persist both before auto-dispatch.
- Effective default behavior after bootstrap is `L2` via `system_level=L2` and `project_level=follow-system`.

Example user `ica.config.json`:
```json
{
  "autonomy": {
    "system_level": "L2"
  }
}
```

Example project `ica.config.json`:
```json
{
  "autonomy": {
    "project_level": "follow-system"
  }
}
```

Compatibility:
- If legacy `autonomy.level` exists and `autonomy.system_level` is missing, treat legacy value as system level for this run and persist it as `autonomy.system_level`.

## Tracking Backend Selection (MANDATORY)

Resolve backend with config-first precedence:

1. Project config: `.agent/tracking.config.json`
2. Global config: `${ICA_HOME}/tracking.config.json`
3. Agent-home config fallback:
- `$HOME/.codex/tracking.config.json`
- `$HOME/.claude/tracking.config.json`
4. Auto-detect GitHub backend
5. Fallback: `.agent/queue/`

Provider values:
- `github`
- `linear` (future)
- `jira` (future)
- `file-based`

Detection pattern:

```bash
TRACKING_PROVIDER=""
for c in ".agent/tracking.config.json" \
         "${ICA_HOME:-}/tracking.config.json" \
         "$HOME/.codex/tracking.config.json" \
         "$HOME/.claude/tracking.config.json"; do
  if [ -n "$c" ] && [ -f "$c" ]; then
    TRACKING_PROVIDER="$(python3 - <<'PY' "$c"

From intelligentcode-ai/skills, MIT.

More from intelligentcode-ai/skills