fix: pedagogical review - add expected output, CLAUDE.md, fix consistency

Address findings from pedagogical review simulating a non-expert user:

- Add CLAUDE.md to project root (was referenced but missing)
- Fix README score from 12/9/1 to 13/8/1 (match feature-map.md)
- Add Expected Output sections to examples 01, 02, 05, 09, 10
- Create pipeline-output/ and briefings/ directories
- Add example ordering guidance in README
- Add plan requirements for examples 11/13 in prerequisites
- Add skill frontmatter explanation in GETTING-STARTED.md
- Explain Cowork/Dispatch with links in cowork-integration
- Expand .gitignore with node_modules and generated output files
- Add model override hints in agent frontmatter comments

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

GETTING-STARTED.md

@@ -14,9 +14,9 @@ Here is exactly what to do.
 
 ## Step 1: Make Claude Code know you (30 minutes)
 
-Open `CLAUDE.md` and replace the demo content with your own
-context. This is the most important file in the entire setup.
-Claude reads it at the start of every session.
+Open `CLAUDE.md` in the project root and replace the demo content
+with your own context. This is the most important file in the entire
+setup. Claude reads it at the start of every session.
 
 Write it like a briefing for a capable new colleague on their
 first day:
@@ -133,6 +133,13 @@ always-on, but covers most situations.
 Skills are what transform Claude Code from "general AI
 assistant" into "my assistant that knows how I work."
 
+### Important: skill file format
+
+Every skill file needs YAML frontmatter between `---` markers at the top.
+Without this, Claude Code will not recognize it as a skill. The `name` field
+is what you type after `/` to run it. The `description` field helps Claude
+decide when to suggest it.
+
 ### Example: Weekly status report
 
 Create `.claude/skills/weekly-status.md`: