---
name: catlog22/maestro-issue
source: https://app.decimal.ai/s/catlog22-maestro-issue@2/SKILL.md
source_sha256: 83b85dce1a5c
---

<purpose>
Intent-driven issue management (renamed from maestro-manage, narrowed to issues). No fixed subcommand grammar — state your intent; the `issue` step classifies it into one operation and extracts the needed parameters:

- **create** — report/record a new issue
- **list** — list issues (with optional filters)
- **show** — view one issue in detail
- **update** — change status/priority/add a note
- **close** — resolve/fail/defer an issue
- **link** — link an issue to a task
- **discover** — automated multi-perspective issue discovery
</purpose>

<dispatch>
Execute the `issue` step inside a v3 Session: open one with `maestro session open "<objective>" --id <slug> --chain issue --participant {p} --actor {a} --request-id {r} --reason "<reason>" --json` and dispatch with fenced `maestro run next --session {session_id} ... --expected-orchestration-revision {rev} --json` (or self-start with `maestro run create issue [args...] --session {session_id} ... --json`), passing the full `$ARGUMENTS` as the step input (repeatable `--arg` / positional passthrough per the command contract). Read context read-only with `maestro session status` / `maestro session resume-view`; `maestro run complete {run_id} ... --advance` publishes outputs and auto-stages knowledge candidates. (v2's `run skill` dispatcher is removed from the v3 surface.)

The step classifies the intent, extracts parameters, and routes to the operation.

- Free-form intent is classified into create / list / show / update / close / link / discover.
- Explicit keywords (`create|list|status|show|update|close|link`) and `--flags` still work as deterministic shortcuts and override inferred values.
- `discover` routes to the dedicated `issue-discover` step.
- Ambiguous intent → the step asks the user to disambiguate.
</dispatch>