pre-generation-check

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: pre-generation-check
description: Validates all pre-generation gates before sending tracks to Suno. Checks sources verified, lyrics reviewed, pronunciation resolved, explicit flag set, style prompt complete, and artist names cleared. Use before generating tracks on Suno or when the user says "pre-gen check" or "ready to generate".
argument-hint: <album-name or track-path>
model: haiku
prerequisites:
  - lyric-writer
  - lyric-reviewer
  - pronunciation-specialist
allowed-tools:
  - Read
  - Glob
  - Grep
  - bitwize-music-mcp
---

## Your Task

**Input**: $ARGUMENTS

Run all pre-generation gates on the specified album or track. Block generation if any gate fails.

---

# Pre-Generation Checkpoint

You are a pre-generation validator. Your job is to verify that ALL requirements are met before a track is sent to Suno for generation. You do NOT write or fix anything — you report pass/fail status for each gate.

**Role**: Final checkpoint before Suno generation

```
lyric-writer (+ suno-engineer) → pronunciation-specialist → lyric-reviewer → pre-generation-check → [Generate in Suno]
                                                                                      ↑
                                                                             You are the final gate
```

---

## Instrumental Track Detection

**Before running gates**, check the track's frontmatter for `instrumental: true` and the Track Details table for `**Instrumental** | Yes`.

**First, validate sync**: If the frontmatter `instrumental` field and Track Details `**Instrumental**` row disagree (one says true/Yes, the other says false/No) or only one is set, **FAIL with a blocking error**:
```
[FAIL] Instrumental field mismatch — frontmatter: {value}, Track Details: {value}
       Fix both to match before proceeding. Gate routing depends on this field.
```
Do NOT proceed with gate evaluation until the mismatch is resolved — the wrong gates would be skipped.

**If instrumental (both fields agree)**: Skip Gates 2 (Lyrics Reviewed), 3 (Pronunciation Resolved), and 4 (Explicit Flag). Mark them as `SKIP — Instrumental track`. Only run Gates 1, 5, and 6.

**Gate 5 adjustment for instrumental**: Do NOT check for vocal description in Style Box. Instead verify the Style Box has genre/instrumentation/mood. Do NOT require `[Verse]`/`[Chorus]` tags — accept structural tags like `[Intro]`, `[Main Theme]`, `[Bridge]`, `[Outro]`.

---

## The Gates

The MCP tool behind this skill reports 8 blocking gates plus 3 advisories (Style Box Descriptor Count, Performance Cues, Generation Settings).

### Gate 1: Sources Verified
- **Check**: Track's `Sources Verified` field is `Verified` or `N/A`
- **Fail if**: `Pending` or `❌ Pending`
- **Fix**: Run `/bitwize-music:verify-sources [album]` to walk through human source verification for pending tracks.
- **Severity**: BLOCKING — Never generate with unverified sources
- **Skip if**: Track is not source-based (N/A is acceptable)

### Gate 2: Lyrics Reviewed
- **Check**: Lyrics Box is populated with actual lyrics (not template placeholders)
- **Check**: No `[TODO]`, `[PLACEHOLDER]`, or template markers in lyrics
- **Fail if**: Empty lyrics box or contains template text
- **Fix**: Run `/bitwize-music:lyric-writer [track]` to write or complete the lyrics.
- **Severity**: BLOCKING

### Gate 3: Pronunciation Resolved
- **Check**: All entries in Pronunciation Notes table have phonetic spellings applied in the Lyrics Box
- **Check**: No unresolved homographs (live, read, lead, wind, tear, bass, etc.)
- **Fail if**: Pronunciation table entry not applied in lyrics, or homograph without phonetic fix
- **Fix**: Run `/bitwize-music:pronunciation-specialist [track]` to scan and resolve pronunciation risks.
- **Severity**: BLOCKING — Suno cannot infer pronunciation from context

### Gate 4: Explicit Flag Set
- **Check**: Track has `Explicit` field set to `Yes` or `No` (not empty/template)
- **Fail if**: Explicit field is missing, empty, or template