feat(linkedin): reduce interactive steps in quick, react, pipeline commands

quick.md:
- Replace 8-option post type menu with context inference
- Auto-select CTA based on post type
- Remove proactive alternative version offering
- AskUserQuestion: 0 in main flow (was 1 implicit menu)

react.md:
- Auto-select strongest angle instead of 3-option AskUserQuestion
- Replace 6-option refinement AskUserQuestion with plain text options
- Same treatment for comparison path (Step 4b)
- AskUserQuestion: 1 in main flow (multi-URL only, was 3)

pipeline.md:
- Skip ideation ask if topic provided with command invocation
- Auto-propose planned topic without AskUserQuestion
- Inline angle selection (auto-select strongest)
- AskUserQuestion: 2 in main flow (ideation fallback + scheduling, was 3)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-04-10 15:18:50 +02:00
commit 10b70dba10
3 changed files with 61 additions and 68 deletions

View file

@ -35,20 +35,20 @@ Read `assets/quick-post-resources.md` for:
## Step 1: Identify Post Type
Ask the user (or infer from context) what triggered this post:
Infer the post type from context — do NOT present a menu. Use these signals:
```
What triggered this post?
| User Signal | Post Type |
|-------------|-----------|
| "Something happened..." / reacting to event | REACTION POST |
| "I noticed..." / pattern observation | OBSERVATION POST |
| "I learned..." / tip or lesson | QUICK TIP POST |
| Asking a question / "I wonder..." | QUESTION POST |
| Strong opinion / "I disagree..." | HOT TAKE POST |
| "I made a mistake..." / failure story | FAILURE POST |
| Shared a link / "I saw this..." | CURATION POST |
| Brief insight, no elaboration needed | ONE-LINER POST |
1. Something happened today -> REACTION POST
2. I noticed something -> OBSERVATION POST
3. I learned something -> QUICK TIP POST
4. I want to hear others -> QUESTION POST
5. I disagree with wisdom -> HOT TAKE POST
6. I made a mistake -> FAILURE POST
7. I saw something worth sharing -> CURATION POST
8. I have a simple insight -> ONE-LINER POST
```
Only ask if truly ambiguous (no discernible intent). Otherwise, state: "This reads as a [TYPE] — proceeding with that format."
## Step 2: Apply 3-Line Formula
@ -104,15 +104,21 @@ Based on post type, use appropriate hook from `assets/quick-post-resources.md`:
- Single powerful statement
- No explanation needed (use sparingly)
## Step 4: Select CTA
## Step 4: Auto-Select CTA
Choose from `assets/quick-post-resources.md`:
Auto-select the best CTA based on post type — do NOT ask:
**Question CTAs:** "What's your take?" | "Anyone else experiencing this?" | "What am I missing?"
| Post Type | Default CTA |
|-----------|------------|
| REACTION / OBSERVATION | "Anyone else seeing this?" |
| QUICK TIP | "What's worked for you?" |
| QUESTION | The question itself IS the CTA |
| HOT TAKE | "Change my mind." |
| FAILURE | "What's your version of this mistake?" |
| CURATION | "Worth a read — what's your take?" |
| ONE-LINER | "Agree or disagree?" |
**Challenge CTAs:** "Change my mind." | "Prove me wrong."
**Share CTAs:** "What's worked for you?" | "Drop your version in the comments."
Reference `assets/quick-post-resources.md` for additional CTA options if the default doesn't fit.
## Step 5: Write and Check
@ -141,7 +147,7 @@ printf '%s' '<FINAL_POST_TEXT>' | node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/clipb
```
Then confirm: "Copied to clipboard."
Offer one alternative version with different hook or angle.
Do NOT proactively offer alternative versions. Only generate alternatives if the user asks.
**State Update:**
After the post is finalized, update `~/.claude/linkedin-thought-leadership.local.md`: