feat(linkedin-studio): S14 — journey layer (create/measure front-doors + 5-journey router), v4.1.0

14a's cold command-rationalization found ZERO redundancy across the 27 commands
(no defensible merge/cut), so the operator reframed S14 from "merge/cut" to
"add a journey layer over the kept atomics".

- Add /linkedin:create + /linkedin:measure — delegate-only guided front-doors
  (Read/Glob/AskUserQuestion only; route to the command that owns the work)
- Re-tier commands/linkedin.md into 5 journeys (Start/Create/Engage/Measure/Grow);
  onboarding/strategy elevated as Start/Grow front-doors; Engage = calendar+firsthour tier
- 14a honesty nits: router now lists firsthour; calendar cross-links to firsthour;
  competitive confirmed UNGATED (the claimed 1K-gating inconsistency was unfounded)
- Lockstep: EXPECT_COMMANDS 27->29, v4.0.0->4.1.0 across plugin.json / README badges /
  plugin+root CLAUDE.md / README / CHANGELOG; new README commands-badge lint guard
- 14a deliverable corrected: multiplatform entry added (26/27 -> 27/27), header counts,
  competitive nit withdrawn
- Independent /trekreview (2 Opus reviewers) raised 3 MAJORs (stale commands badge,
  router competitive self-contradiction, STATE.md count) — ALL remediated in-session;
  verdict ALLOW

Gate: test-runner.sh 74/0/0; node --test 98/98; commands=29; v4.1.0 consistent.
Additive/minor — no command removed/renamed/behavior-changed; reload registers create+measure.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-05-30 21:27:06 +02:00
commit baca30feb1
16 changed files with 885 additions and 208 deletions

View file

@ -0,0 +1,66 @@
---
name: linkedin:create
description: |
Content-creation front-door — one guided entry for when you want to make something
but haven't picked the format yet. Asks what you want to create and routes you to the
command that owns that format (post, quick, react, carousel, video, multiplatform,
batch, or the long-form newsletter). It does NOT draft anything itself — it hands off
to the command that owns the work, so each format keeps its own voice rules and
quality gates.
Triggers on: "create", "make something", "create content", "what should I make",
"new content", "help me create", "i want to post something", "linkedin create".
allowed-tools:
- Read
- Glob
- AskUserQuestion
---
# Create — Content Front-Door
You are the entry point for the **Create** journey. The user wants to make content but
may not know which format or command fits. Your job: identify the intent in one
question and route to the command that owns the work. **You do not draft here.**
## Step 0: Quick context (optional)
If `~/.claude/linkedin-studio.local.md` exists, you may glance at the planned next
topic and recent pillars to make a smarter suggestion — but keep it to one line and
do not block on it.
## Step 1: Identify what they want to create
If the user's message already names a format (e.g. "a carousel about X", "react to
this URL", "a video script") OR hands you a URL, skip the question and route directly
per the map below.
Otherwise use `AskUserQuestion`**"What do you want to create?"**
1. **A post** — a full, substantial post (angle → draft → refine) → `/linkedin:post`
2. **A quick post** — a fast 5-minute post or a templated post-type → `/linkedin:quick`
3. **React to something** — turn a URL / article / news into a post → `/linkedin:react`
4. **A carousel** — a multi-slide / document post → `/linkedin:carousel`
5. **A video script** — talking-head / screen-recording / slideshow → `/linkedin:video`
6. **Adapt existing content** — for Twitter/X, slides, YouTube → `/linkedin:multiplatform`
7. **A whole week** — batch 35 posts in one session → `/linkedin:batch`
8. **Long-form** — newsletter edition, essay, or series article → `/linkedin:newsletter`
## Step 2: Route
State the chosen command and one line of why, then **proceed into that command's
workflow** (route to `/linkedin:<target>` and begin it). Do NOT inline or duplicate
the target's steps — each creation command owns its own workflow, voice rules, and
quality gates.
| Intent | Command |
|--------|---------|
| Substantial post | `/linkedin:post` |
| Quick / templated post | `/linkedin:quick` |
| React to a URL / article | `/linkedin:react` |
| Carousel / document | `/linkedin:carousel` |
| Video script | `/linkedin:video` |
| Cross-platform adaptation | `/linkedin:multiplatform` |
| A full week | `/linkedin:batch` |
| Long-form (newsletter / essay / series) | `/linkedin:newsletter` |
**Long-form lock:** newsletters, essays, and series articles are owned end-to-end by
`/linkedin:newsletter` — the single long-form entry point. Never draft long-form here.