// Implement focused Audiobook Organizer features across CLI, organizer core, TUI, web UI, or ABS workflows while following issue, branch, tests, docs, and changelog rules.
| name | abo-feature |
| description | Implement focused Audiobook Organizer features across CLI, organizer core, TUI, web UI, or ABS workflows while following issue, branch, tests, docs, and changelog rules. |
| metadata | {"short-description":"Implement ABO features"} |
You are the Audiobook Organizer feature engineer.
Read AGENTS.md, references/abo-assistant/common.md, and references/abo-assistant/testing.md.
$abo-issue-create logic.git status --short --branch shows a dedicated non-master issue branch before editing.references/abo-assistant/testing.md; mocked UI/API tests may supplement but must not be the only proof unless the maintainer explicitly accepts the documented gap.CHANGELOG.md, and test/abs/test-matrix.md when applicable. For functionality or workflow changes, follow $abo-docs guidance by checking both README.md and the static docs site source under web/src/content/docs/, plus mirrored docs/ pages when present.$abo-pr and $abo-issue-closeout so the PR merges back into master and the linked issue closes.Route current local browser UI work to $abo-web-ui and ABS harness behavior to $abo-abs-tests.
Work on Audiobook Organizer Audiobookshelf harness validation, ABS E2E tests, matrix updates, reset contracts, and ABS-facing behavior verification.
Reproduce, fix, and verify Audiobook Organizer bugs with focused tests first, preserving dry-run, undo, logging, metadata, layout, web, and ABS invariants.
Update Audiobook Organizer documentation, AGENTS.md, changelog entries, and maintainer-facing workflow notes while keeping repo-local skill references consistent.
Close out Audiobook Organizer issues with verification, status comments, and PR-aware hygiene.
Verify that an Audiobook Organizer issue is done by checking acceptance criteria, code changes, tests, docs, changelog, and ABS matrix obligations.
Draft or update Audiobook Organizer PR descriptions with issue closure, summary, tests, docs/changelog status, and follow-up notes.