resume
Finds an album by name and shows detailed status with next steps. Use when the user mentions an album name or wants to continue previous work.
What this skill does
# Resume Album Work
**Purpose**: Find an album and resume work where you left off.
**Usage**:
```
/bitwize-music:resume <album-name>
/bitwize-music:resume my-album
/bitwize-music:resume "demo album"
```
**When to use**: When user wants to continue working on an existing album.
---
## Instructions
When this skill is invoked with an album name:
### Step 1: Find the Album via MCP
1. Call `find_album(name)` — fuzzy match by name, slug, or partial (case-insensitive)
2. If not found: MCP returns available albums — suggest closest match or `/bitwize-music:new-album`
3. If multiple matches: list all with paths, ask user which one
4. If MCP returns stale/missing cache error: call `rebuild_state()` then retry
### Step 2: Get Album Progress
1. Call `get_album_progress(album_slug)` — returns track counts by status, completion percentage, and detected workflow phase
2. Call `list_tracks(album_slug)` — returns per-track details (status, has_suno_link, sources_verified)
### Step 3: Update Session Context
Call `update_session(album=album_slug, phase=detected_phase)` to set the active album and phase.
### Step 4: Determine Current Phase
Based on album and track statuses, identify the workflow phase:
| Album Status | Track Statuses | Current Phase |
|--------------|----------------|---------------|
| Concept | Most "Not Started" | Planning - Need to fill in album README and create tracks |
| Research Complete | Some "Sources Pending" | Verification - Need human verification of sources (documentary albums) |
| Sources Verified | All sources verified | Ready to Write - Sources cleared, begin lyrics (documentary albums) |
| In Progress | Mixed, some "Not Started" | Writing - Need to complete lyrics (or route instrumental tracks to suno-engineer) |
| In Progress | Some "Sources Pending" | Verification - Need human verification of sources |
| In Progress | All have lyrics | Ready to Generate - Run Ready to Generate checkpoint |
| In Progress | Some "Generated" | Generating - Continue generating on Suno. Check Generation Logs for rejected tracks needing regeneration |
| In Progress | All "Generated", none "Final" | Review & Approve - Listen to generated tracks, mark keepers with ✓, regenerate rejected ones |
| Complete | All "Final" | Mastering - Ready to master audio |
| Released | All "Final" | Released - Album is live |
**Note**: Non-documentary albums skip `Research Complete` and `Sources Verified` — they go directly from `Concept` → `In Progress`.
### Step 5: Report to User
Present a clear status report:
```
📁 Album: [Album Title]
Location: {content_root}/artists/{artist}/albums/{genre}/{album}/
Status: [Album Status]
📊 Progress:
- Tracks: [X completed / Y total] ([N vocal, M instrumental])
- Not Started: X
- In Progress: Y
- Generated: Z
- Final: N
📍 Current Phase: [Phase Name]
✅ What's Done:
- [List completed items]
⏭️ Next Steps:
1. [Specific action 1]
2. [Specific action 2]
3. [Specific action 3]
Ready to continue? Tell me what you'd like to work on.
```
### Step 6: Recommend the Single Best Next Action
Pick ONE clear recommendation from the decision tree below. Don't list 5 options — pick the best one, include the skill name, and be specific about which track.
**Decision Tree** (evaluate top-to-bottom, first match wins):
**Instrumental detection**: Check each track's frontmatter for `instrumental: true` or Track Details table for `**Instrumental** | Yes`. Instrumental tracks skip the lyrics workflow entirely and go straight to `/bitwize-music:suno-engineer`.
```
Album Status = "Concept"
→ "Define the album concept. Run /bitwize-music:album-conceptualizer"
Album Status = "Research Complete"
→ Any tracks Sources Pending?
YES → "Sources need verification. Run /bitwize-music:verify-sources [album]"
NO → Any "Not Started" tracks instrumental?
YES → "Create Style Box for instrumental track [name]. Use /bitwize-music:suno-engineer"
NO → "Ready to write! Pick a track and use /bitwize-music:lyric-writer"
Album has tracks with "Not Started"
→ Is the first not-started track instrumental?
YES → "Create Style Box for [track]. Use /bitwize-music:suno-engineer directly (instrumental track)"
NO → "Write lyrics for [first not-started track]. Use /bitwize-music:lyric-writer"
Album has tracks with "In Progress" (lyrics partially written)
→ "Finish lyrics for [first in-progress track]. Use /bitwize-music:lyric-writer"
Album has tracks with "Sources Pending"
→ "Verify sources for [track]. Run /bitwize-music:verify-sources [album]"
All tracks have lyrics (or Style Box for instrumentals), none generated
→ Mixed album (vocal + instrumental)?
YES → "All tracks ready! Run /bitwize-music:pronunciation-specialist on vocal tracks, then /bitwize-music:lyric-reviewer, then /bitwize-music:pre-generation-check to validate all gates (instrumental tracks auto-skip lyrics gates)."
NO → "All lyrics complete! Style prompts should be ready. Run /bitwize-music:pronunciation-specialist to check for pronunciation risks, then /bitwize-music:lyric-reviewer for final QC, then /bitwize-music:pre-generation-check to validate all gates before generating on Suno."
Some tracks generated, some not
→ Any Generated tracks without ✓ in Generation Log Rating?
YES → "Track [name] was generated but not approved. Listen and decide:
- Happy? Mark ✓ in Generation Log and set Status: Final
- Not happy? Log the reason, then:
Style issue → /bitwize-music:suno-engineer to revise Style Box
Lyrics issue → /bitwize-music:lyric-writer to fix, then regenerate
Bad luck → Regenerate on Suno with same settings (it's non-deterministic)"
NO → "Generate [first un-generated track] on Suno. Use /bitwize-music:suno-engineer"
All tracks generated, none Final
→ "All tracks generated! Listen to each track and approve:
- Mark keepers with ✓ in Generation Log Rating column
- Reject and regenerate any that don't meet quality standards
- Once all have ✓, batch-approve:
Use update_track_field(album_slug, track_slug, 'status', 'Final') for each approved track.
Once all Final, album advances to Complete automatically."
All tracks generated, some Final
→ Any Generated (non-Final) tracks without ✓?
YES → "Review track [name] — listen and approve (✓) or regenerate"
NO → "All tracks approved! Batch-approve: update_track_field(album_slug, track_slug, 'status', 'Final') for each.
Then import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"
All tracks Final
→ "All tracks approved! Import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"
Album Status = "Complete"
→ "Album is complete! Release with /bitwize-music:release-director"
Album Status = "Released"
→ "This album is released! Consider /bitwize-music:promo-director for promotional content"
→ Also suggest: "Start a new album? Check /bitwize-music:album-ideas list"
```
**Format the recommendation as:**
```
RECOMMENDED NEXT ACTION:
[Clear, specific instruction with skill name and track name]
WHY:
[One sentence explaining why this is the right next step]
```
### When No Album Specified (No Arguments)
If invoked without an album name:
1. Call `get_session()` — check `last_album` from session context, resume that album
2. If no session context, call `list_albums()` to find all in-progress albums
3. Prioritize: closest to completion > unblocked work > last worked on
4. If no albums exist, suggest `/bitwize-music:new-album`
Present a multi-album summary if multiple are in progress:
```
You have X albums. Here's the most actionable:
PRIORITY 1: [album-name] ([genre])
Status: [status] | Progress: [X/Y tracks]
→ [Recommended action]
Also in progress:
- [album-2] — [brief status]
```
---
## Examples
### Example 1: Album in Writing Phase
```
/bitwize-muRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.