ワンクリックで
ask-abb
Pick the next Audiobook Boss flow when the user asks which step to use. Use for smell-to-ship routing in audiobook-boss only.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Pick the next Audiobook Boss flow when the user asks which step to use. Use for smell-to-ship routing in audiobook-boss only.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Canonical metadata strategy for Audiobook Boss. Use when changing tag mappings, metadata intent behavior, or ABS/Plex/Apple interoperability rules.
Resolve ABB external-library/API uncertainty for Effect, Svelte, Tauri, Specta, or tauri-specta when implementation, IPC contract, codegen, installed-version, or upstream-source behavior affects the work. Use route cards, Context7, lockfiles, and repos/* for the active question only.
Audit and fix Audiobook Boss resource-lifetime foot-guns with high bug potential. Use when the user asks to hunt for lifecycle bugs, file-handle contention, Windows/cross-platform file behavior, temp-file cleanup, process lifetime, FFmpeg/mp4ameta reopen issues, rename/replace semantics, or "similar in-kind" high-ROI issues.
ABB repo-grounded alignment when substantial work needs a locked decision or GitHub issue capture. Inspect repo truth first; at most two action-changing questions. Default capture is GitHub issues.
Audiobook Boss release workflow for deciding whether changes need a formal version/changelog release, preparing release metadata, validating the local app or DMG artifact, tagging, and publishing manually. Use when the user mentions release, version bump, changelog, tag, GitHub Release, DMG, publish, ship, release notes, or asks whether a change should be released.
| name | ask-abb |
| description | Pick the next Audiobook Boss flow when the user asks which step to use. Use for smell-to-ship routing in audiobook-boss only. |
Precondition: docs/agents/issue-tracker.md and docs/agents/triage-labels.md exist in the repo.
decision-alignment — repo-grounded explore. Read docs/system-map.md, docs/ubiquitous-language.md, owning code. Chat first; capture a GitHub issue only when explicit.abb-library-research (user invokes). Answer in chat.improve-codebase-architecture (user invokes). Report in OS temp; return to step 1 if capture is next.docs/agents/issue-tracker.md and decision-alignment/references/issue-template.md. Label ready-for-agent when complete without chat.to-issues (user invokes).Keep explore and capture in one window when practical. After to-issues, fresh session per child issue. handoff to OS temp when switching threads — link issues; do not paste bodies.
grill-medocs/agents/triage-labels.mdagents-md-stewardimprove-codebase-architecture (user invokes), then step 1 if capturingdocs/ubiquitous-language.mddocs/system-map.mddocs/DECISIONS.mddocs/api-map.mdDefault: ABB repo work → step 1. Not repo-grounded → grill-me.