docs: add mandatory workflow rules for specs and implementations

Add critical section to CLAUDE.md documenting the correct process for
creating new specifications and implementations. This prevents bypassing
the automated GitHub Actions pipeline which causes:

- Missing quality_score in metadata
- Missing preview images in GCS
- No impl:{library}:done labels on issues
- Issues staying open when complete

Includes DO/DON'T table and batch creation example.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: MarkusNeusinger

CLAUDE.md

@@ -8,6 +8,92 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 - **GitHub Actions workflows ARE allowed to commit/push** - When running as part of `spec-*.yml` or `impl-*.yml` workflows, creating branches, commits, and PRs is expected and required.
 - **Always write in English** - All output text (code comments, commit messages, PR descriptions, issue comments, documentation) must be in English, even if the user writes in another language.
 
+## CRITICAL: Mandatory Workflow for New Specs and Implementations
+
+**NEVER bypass the automated workflow!** All specifications and implementations MUST go through the GitHub Actions pipeline.
+
+### Creating New Specifications - CORRECT Process
+
+```
+1. Create GitHub Issue with descriptive title (NO spec-id in title!)
+   ✅ "Annotated Scatter Plot with Text Labels"
+   ❌ "[scatter-annotated] Annotated Scatter Plot"  ← WRONG: Don't include spec-id
+
+2. Add `spec-request` label to the issue
+
+3. WAIT for spec-create.yml to:
+   - Analyze the request
+   - Check for duplicates (will close if duplicate exists)
+   - Assign a unique spec-id
+   - Generate tags automatically
+   - Create PR with specification.md and specification.yaml
+
+4. Add `approved` label to the ISSUE (not the PR!)
+   - This triggers the merge job in spec-create.yml
+
+5. WAIT for automatic merge and `spec-ready` label
+```
+
+### Generating Implementations - CORRECT Process
+
+```
+1. After spec has `spec-ready` label, trigger bulk-generate:
+   gh workflow run bulk-generate.yml -f specification_id=<spec-id> -f library=all
+
+2. WAIT for the full pipeline to complete:
+   impl-generate → impl-review → (impl-repair if needed) → impl-merge
+
+3. DO NOT manually merge PRs!
+   - impl-merge.yml handles merging, metadata creation, and GCS promotion
+   - Manual merging breaks: quality_score, review data, GCS images
+```
+
+### What You Must NEVER Do
+
+| ❌ DON'T | ✅ DO INSTEAD |
+|----------|---------------|
+| Manually create `plots/{spec-id}/` directories | Let `spec-create.yml` create them |
+| Manually write `specification.md` files | Let `spec-create.yml` generate them |
+| Include `[spec-id]` in issue title | Use descriptive title only |
+| Add `approved` label to PRs | Add `approved` label to ISSUES |
+| Run `gh pr merge` on implementation PRs | Let `impl-merge.yml` handle it |
+| Manually create `metadata/*.yaml` files | Let `impl-merge.yml` create them |
+| Upload images to GCS manually | Let workflows handle GCS |
+
+### Why This Matters
+
+Manual intervention causes:
+- `quality_score: null` in metadata (no AI review)
+- Missing preview images in GCS production folder
+- No `impl:{library}:done` labels on issues
+- Broken database sync (missing review data)
+- Issues staying open when complete
+
+### Batch Creation Example
+
+```bash
+# Step 1: Create 5 issues (NO spec-id in title!)
+for title in "Radar Chart" "Treemap" "Sunburst Chart" "Sankey Diagram" "Chord Diagram"; do
+  gh issue create --title "$title" --label "spec-request" --body "New plot type request"
+done
+
+# Step 2: Wait for spec-create to process each issue
+# Check: gh issue list --label "spec-request" --state open
+
+# Step 3: Add approved labels to ISSUES (after reviewing spec PRs)
+# gh api repos/OWNER/REPO/issues/NUMBER/labels -f labels[]=approved
+
+# Step 4: Wait for specs to merge and get spec-ready label
+
+# Step 5: Trigger bulk-generate for each spec
+# gh workflow run bulk-generate.yml -f specification_id=<spec-id> -f library=all
+
+# Step 6: Monitor - DO NOT manually merge!
+# gh run list --workflow=impl-generate.yml
+# gh run list --workflow=impl-review.yml
+# gh run list --workflow=impl-merge.yml
+```
+
 ## Project Overview
 
 **pyplots** is an AI-powered platform for Python data visualization that automatically discovers, generates, tests, and maintains plotting examples. The platform is specification-driven: every plot starts as a library-agnostic Markdown spec, then AI generates implementations for all supported libraries.