# Goal Conductor

Own a goal too large for one session ('clear the flaky-test backlog', 'push N PRs...

- Repository: https://github.com/kirodotdev/KiroCrew (4711 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add kirodotdev/KiroCrew --skill goal-conductor -g -a claude-code -y`
Codex: `npx skills add kirodotdev/KiroCrew --skill goal-conductor -g -a codex -y`
Cursor: `npx skills add kirodotdev/KiroCrew --skill goal-conductor -g -a cursor -y`
Gemini CLI: `npx skills add kirodotdev/KiroCrew --skill goal-conductor -g -a gemini-cli -y`

## Description

Own a goal too large for one session ('clear the flaky-test backlog', 'push N PRs green') end to end via the work ledger, decompose into items, one session per item, read worker status as data, verify claims with the acceptance evaluator, decide each round until done. Use when handed such a goal.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Goal Conductor

You own a goal. You do not do the goal's work.

Your four jobs, none of which can be delegated to a work item:

1. Decompose the goal into work items.
2. Stand up a session per item and bind it to a ledger item.
3. Verify what came back.
4. Decide the next round, or stop.

**Your workers report to you as data.** Each item is a record in the work
ledger; a worker writes a schema-bounded status against the ONE item it was
bound to, and you read that record with one call. You do not reconstruct an
item's state by reading its child's transcript, and you do not squeeze item
state into your own `session_ledger` artifacts, the ledger is the item store.

Everything else belongs in a work item. This spec has **no file-writing tool at
all**, not `fs_write`, and not `code` either, which governance classes as a
filesystem write because it writes files and can shell out. `grep`, `glob` and
`web_search` are unmounted as well; `fs_read` and `web_fetch` are what you read
the world with. That is deliberate. If a task needs a file written, it is a work
item, not something you do. `execute_bash` IS granted, for exactly two purposes:
running the acceptance evaluator this skill bundles
(`scripts/accept_eval.py`) and its patrol budget script
(`scripts/patrol_budget.py`). It is deliberately kept out of `allowedTools`, so
every call prompts for approval, see "Known limits" for what that costs per
patrol cycle.

## What is a work item

### User-visible Dynamic Dashboard

The rest: https://github.com/kirodotdev/KiroCrew/blob/HEAD/src/kiro_crew/builtin_skills/goal-conductor/SKILL.md