Reprendre le travail sur un album

VérifiéSûr

Recherche un album via MCP, affiche l'avancement par piste et détecte la phase de travail en cours pour reprendre là où vous vous êtes arrêté.

Spar Skills Guide Bot
ContenuIntermédiaire
14/09/2026
Claude Code
#music-production#album-workflow#project-resume#mcp#status-reporting

Recommandé pour

Synthèse automatique

Recherche un album par son nom via le serveur MCP bitwize-music et affiche son avancement, sa phase de travail et les prochaines étapes pour reprendre le travail.

Points forts

  • Correspondance floue sur le nom, le slug ou une partie du nom, avec gestion des homonymes.
  • Rapport de statut détaillé : statut de l’album, progression des pistes, phase détectée et éléments terminés.
  • Met à jour le contexte de session avec l’album et la phase actifs.
  • Recommande une seule action suivante concrète plutôt qu’une longue liste d’options.

Limites

  • Dépend fortement du serveur MCP bitwize-music et de son cache ; une erreur de cache nécessite une reconstruction.
  • Ne concerne que les albums gérés dans l’arborescence bitwize-music.
  • La recommandation repose sur des statuts standard et peut être imprécise pour des états atypiques.
Quand l'utiliser

À utiliser lorsqu’on reprend un album existant et qu’on veut savoir où en est le travail et quelle étape lancer ensuite.

Quand l'éviter

À ne pas utiliser pour créer un nouvel album ou pour travailler sur des fichiers musicaux hors du système bitwize-music.

Analyse de sécurité

Sûr
Score qualité92/100

The skill instructs read-only queries via a music MCP and file reads/globs to resume album work. Although Bash is declared as an allowed tool, the instructions do not invoke or suggest any shell commands, destructive actions, network exfiltration, or obfuscation. The MCP calls are domain-specific and non-destructive.

Aucun point d'attention détecté

Comment cette analyse est faite

Exemples

Resume by album name
/bitwize-music:resume my-album
Check where I left off
Resume work on "demo album" and tell me the current phase and next step.
Find album with partial name
Where did I leave off on Night Drive? Show progress and what I should do next.

name: resume description: 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. argument-hint: <album-name> model: claude-sonnet-4-6 allowed-tools:

  • Read
  • Glob
  • Bash
  • bitwize-music-mcp

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-music:resume my-album

📁 Album: My Album
   Location: ~/bitwize-music/artists/bitwize/albums/rock/my-album/
   Status: In Progress

📊 Progress:
   - Tracks: 3 completed / 8 total
   - Not Started: 3
   - In Progress: 2
   - Final: 3

📍 Current Phase: Writing Lyrics

✅ What's Done:
   - Tracks 1-3 have final lyrics
   - Album concept and tracklist defined

⏭️ Next Steps:
   1. Complete lyrics for Track 4 (in progress)
   2. Complete lyrics for Track 5 (in progress)
   3. Write lyrics for Tracks 6-8

Ready to continue? Tell me which track you'd like to work on.

Example 2: Album Ready for Generation

/bitwize-music:resume demo-album

📁 Album: Demo Album
   Location: ~/bitwize-music/artists/bitwize/albums/electronic/demo-album/
   Status: In Progress

📊 Progress:
   - Tracks: 8 / 8 total (all lyrics complete)
   - Final: 8

📍 Current Phase: Ready to Generate

✅ What's Done:
   - All 8 tracks have complete lyrics
   - All lyrics phonetically reviewed
   - Suno Style and Lyrics boxes filled

⏭️ Next Steps:
   1. Run Ready to Generate checkpoint (I'll verify everything)
   2. Start generating on Suno
   3. Log generation attempts

Shall I run the Ready to Generate checkpoint now?

Example 3: Album Not Found

/bitwize-music:resume my-album

❌ Album 'my-album' not found.

Available albums:
- demo-album (electronic) - In Progress
- example-tracks (hip-hop) - Complete

Did you mean one of these? Or use /bitwize-music:new-album to create a new album.

Implementation Notes

  • Use MCP tools - find_album, get_album_progress, list_tracks, update_session instead of reading state.json directly
  • Case-insensitive matching - "Sample-Album" should match "sample-album"
  • Handle missing albums gracefully - List what exists, don't error
  • Be specific about next steps - Don't just say "continue working", say exactly what to do
  • Include full paths - User needs to know where files are located
  • Use emojis sparingly - Only for section headers in the report

Model

Use Sonnet 4.5 - This is a coordination/reporting task, not creative work.

Du fichier au premier essai

Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.

Consulter la source et ses fichiers annexes

Ce téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.

1. Télécharger le fichier

Télécharger SKILL.md

Depuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/resume-album-work-mu0qzofu/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.

Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.

mkdir -p '.skill-downloads/resume-album-work-mu0qzofu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/resume-album-work-mu0qzofu/download' --output '.skill-downloads/resume-album-work-mu0qzofu/SKILL.md.part' && mv '.skill-downloads/resume-album-work-mu0qzofu/SKILL.md.part' '.skill-downloads/resume-album-work-mu0qzofu/SKILL.md'

2. Vérifier les prérequis

Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.

Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.

Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.

3. Charger la skill

Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.

Claude Code
test -f '.skill-downloads/resume-album-work-mu0qzofu/SKILL.md' && test -s '.skill-downloads/resume-album-work-mu0qzofu/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/resume' && cp -R '.skill-downloads/resume-album-work-mu0qzofu' '.claude/skills/resume'

OpenSkills

OpenSkills doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.

Installation officielle d’OpenSkills
openskills install './.skill-downloads/resume-album-work-mu0qzofu'

openskills read 'resume-album-work-mu0qzofu'

La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.

Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.

openskills sync

Mode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.

4. Faire un premier essai

Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :

Lis .skill-downloads/resume-album-work-mu0qzofu/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.

Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.

Skills similaires