refactor: rewrite Example 14 as genuine capstone and fix skill creation

Example 14 completely rewritten. Was: GETTING-STARTED.md repeated
(one skill + phone + cron). Now: a 7-phase system design that
produces a complete personal agent ecosystem (custom agents,
multi-agent pipeline, custom hooks, automation, phone delivery).

Requires accumulated knowledge from examples 01-13. Includes:
- Phase 1: Map your work (design before building)
- Phase 3: Custom agent team created via Claude (not manually)
- Phase 4: Pipeline skill chaining agents into complete workflow
- Phase 5: Custom security hooks for user's context
- Phase 7: Test on real work with evaluation rubric
- Three concrete persona examples (marketing, engineering, consulting)

GETTING-STARTED.md Step 4: replaced manual file creation with
"tell Claude to create the skill" workflow. Skills, agents, and
hooks should always be created by asking Claude, not by hand.

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

GETTING-STARTED.md

@@ -149,105 +149,79 @@ always-on, but covers most situations.
 
 ---
 
-## Step 4: Write your first personal skill (15 minutes)
+## Step 4: Create your first personal skill (15 minutes)
 
-Skills are what transform Claude Code from "general AI
-assistant" into "my assistant that knows how I work."
+Skills transform Claude Code from "general AI assistant" into
+"my assistant that knows how I work." You do not write skill
+files by hand. You describe what you need and let Claude create
+the file with the correct format.
 
-### Important: skill file format
+### How it works
 
-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.
+Tell Claude what you want the skill to do. It creates the file
+with proper YAML frontmatter (required for Claude Code to
+recognize it as a skill) and markdown body.
 
 ### Example: Weekly status report
 
-Create `.claude/skills/weekly-status.md`:
-
-```markdown
----
-name: weekly-status
-description: Generate my weekly status report from git
-  activity, project files, and current priorities.
----
-
-# Weekly Status Report
-
-Generate a status report for my manager covering this week.
-
-## Steps
+```
+Create a skill called "weekly-status" that generates my weekly
+status report. It should:
 1. Read CLAUDE.md for current priorities
-2. Run `git log --oneline --since="7 days ago"` to see
-   what changed this week
-3. Check for any files named TODO, ROADMAP, or similar
-4. Write a concise report with:
-   - What was completed
-   - What is in progress
-   - What is blocked or needs input
-   - Plan for next week
-
-## Format
-- Bullet points, not paragraphs
-- Lead with wins
-- Be honest about blockers
-- Under 300 words
+2. Check git log for this week's activity
+3. Look for TODO or ROADMAP files
+4. Write a concise report: what was completed, what is in
+   progress, what is blocked, plan for next week
+Format: bullet points, under 300 words, lead with wins.
+Save it to .claude/skills/weekly-status.md
 ```
 
-Now you can run `/weekly-status` every Monday morning.
-Or text "Run /weekly-status" from your phone.
+Claude creates the file. Now you can run `/weekly-status` every
+Monday morning. Or text "Run /weekly-status" from your phone.
 
 ### Example: Research and save
 
-Create `.claude/skills/deep-research.md`:
-
-```markdown
----
-name: deep-research
-description: Research a topic thoroughly, verify claims,
-  and save a structured summary with sources.
----
-
-# Deep Research
-
-Research the given topic. Verify every claim.
-
-## Steps
-1. Search the web for 3-5 targeted queries
-2. Read the top results
-3. Cross-reference claims across sources
-4. Write a structured summary to
-   `research/[topic-slug]-[date].md`
-
-## Output format
-### Key findings
-- [finding] ([source])
-
-### Details
-[longer explanation with citations]
-
-### What I could not verify
-[be explicit about gaps]
-
-### Sources
-- [title] - [url]
+```
+Create a skill called "deep-research" that researches a given
+topic thoroughly. It should search the web, cross-reference
+claims across sources, and write a structured summary to
+research/[topic-slug]-[date].md with key findings, details,
+what could not be verified, and source URLs.
+Save it to .claude/skills/deep-research.md
 ```
 
 ### Example: Daily briefing
 
-The repo already has `.claude/skills/daily-briefing.md`.
-Customize it: add your news topics, your project context,
-whatever you want to know first thing in the morning.
+The repo already has `.claude/skills/daily-briefing.md`. To
+customize it, just tell Claude:
 
-### How to think about skills
+```
+Update the daily-briefing skill to include [your news topics],
+[your project context], and [what you want to know each morning].
+```
 
-A skill is worth writing when you:
+### Iterating on skills
+
+The first version rarely nails it. Run the skill, read the output,
+and tell Claude what to fix:
+
+```
+The weekly-status output is too long. Update the skill to cap
+each section at 3 bullets and total output at 200 words.
+```
+
+Claude updates the skill file. Run it again. Most skills take
+2-3 iterations to produce output you are happy with.
+
+### When to create a skill
+
+A skill is worth creating when you:
 - Do the same task more than twice a week
-- Explain the same instructions to Claude repeatedly
+- Find yourself explaining the same instructions to Claude
 - Want consistent output format every time
 - Want to trigger something from your phone with one message
 
-Start with 2-3 skills. Add more as you notice patterns.
+Start with 1-2 skills. Add more as you notice patterns.
 
 > **See it in action:** [Example 06](examples/06-multi-agent/prompt.md)
 > shows the researcher-writer-reviewer agent pattern that makes complex