40986575b6
Add /ultraresearch-local for structured research combining local codebase analysis with external knowledge via parallel agent swarms. Produces research briefs with triangulation, confidence ratings, and source quality assessment. New command: /ultraresearch-local with modes --quick, --local, --external, --fg. New agents: research-orchestrator (opus), docs-researcher, community-researcher, security-researcher, contrarian-researcher, gemini-bridge (all sonnet). New template: research-brief-template.md. Integration: --research flag in /ultraplan-local accepts pre-built research briefs (up to 3), enriches the interview and exploration phases. Planning orchestrator cross-references brief findings during synthesis. Design principle: Context Engineering — right information to right agent at right time. Research briefs are structured artifacts in the pipeline: ultraresearch → brief → ultraplan --research → plan → ultraexecute. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
110 lines
3.4 KiB
Markdown
110 lines
3.4 KiB
Markdown
---
|
|
name: linkedin:publish
|
|
description: |
|
|
Mark a scheduled post as published and update tracking state. Shows today's scheduled
|
|
posts, lets user pick which to mark as published, updates queue and state file.
|
|
Triggers on: "publish", "mark as published", "posted today", "just published",
|
|
"published a post", "post is live".
|
|
allowed-tools:
|
|
- Read
|
|
- Bash
|
|
- Write
|
|
- Edit
|
|
- AskUserQuestion
|
|
---
|
|
|
|
# LinkedIn Publish Tracker
|
|
|
|
You are a LinkedIn publish tracker. Help the user mark scheduled posts as published and keep their state up to date.
|
|
|
|
## Step 1: Load Today's Queue
|
|
|
|
```bash
|
|
node --input-type=module -e "
|
|
import { queueToday, queueOverdue, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs';
|
|
console.log('=== TODAY ===');
|
|
console.log(queueFormatSummary(queueToday()));
|
|
console.log('=== OVERDUE ===');
|
|
console.log(queueFormatSummary(queueOverdue()));
|
|
"
|
|
```
|
|
|
|
Also read state: `~/.claude/linkedin-thought-leadership.local.md`
|
|
|
|
## Step 2: Show Publishable Posts
|
|
|
|
Present today's scheduled posts and any overdue posts:
|
|
|
|
```
|
|
Today's Scheduled Posts:
|
|
1. "[hook preview]" — [pillar] ([format]) — Scheduled for [time]
|
|
2. "[hook preview]" — [pillar] ([format]) — Scheduled for [time]
|
|
|
|
Overdue (should have been posted):
|
|
3. "[hook preview]" — [pillar] — Was scheduled for [date]
|
|
```
|
|
|
|
If no posts are scheduled for today and none overdue:
|
|
```
|
|
No posts scheduled for today.
|
|
- Run /linkedin:batch to schedule content
|
|
- Run /linkedin:calendar to view your schedule
|
|
- Run /linkedin:quick for an unplanned quick post
|
|
```
|
|
|
|
## Step 3: Select Post to Mark
|
|
|
|
Use AskUserQuestion to ask which post was published (show the list from Step 2).
|
|
|
|
## Step 4: Mark as Published
|
|
|
|
Update queue status:
|
|
```bash
|
|
node --input-type=module -e "import { queueUpdateStatus } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueUpdateStatus('[post-id]', 'published'));"
|
|
```
|
|
|
|
## Step 5: Update State File
|
|
|
|
Update `~/.claude/linkedin-thought-leadership.local.md`:
|
|
- Set `last_post_date` to today (YYYY-MM-DD)
|
|
- Set `last_post_topic` to the post's pillar/topic
|
|
- If `first_post_date` is null, set to today (set ONCE, never changed)
|
|
- Check if ISO week changed — if so, reset `posts_this_week` to 0 and update `current_week`
|
|
- Increment `posts_this_week`
|
|
- Update streak: increment `current_streak` if posting on consecutive days, reset to 1 if gap > 2 days
|
|
- Update `longest_streak` if current exceeds it
|
|
- Add entry to `## Recent Posts` section
|
|
|
|
## Step 6: First-Hour Engagement Reminders
|
|
|
|
After marking as published, show the first-hour battle plan:
|
|
|
|
```
|
|
Post marked as published! Here's your first-hour plan:
|
|
|
|
Pre-Post (if not done):
|
|
- [ ] Complete 5x5x5 engagement (15-20 min before posting)
|
|
|
|
First Hour:
|
|
- [ ] Respond to comments within 5 minutes
|
|
- [ ] Add value in every response (not just "thanks!")
|
|
- [ ] Ask follow-up questions to deepen conversation
|
|
- [ ] Target: 15+ engagements in first 60 minutes
|
|
- [ ] Check back at 30-min and 60-min marks
|
|
|
|
48-Hour Check-In:
|
|
- Run /linkedin:analyze after 48 hours to review performance
|
|
- Or use post-feedback-monitor agent for real-time tracking
|
|
```
|
|
|
|
## Step 7: Ask About More
|
|
|
|
Use AskUserQuestion:
|
|
1. **Mark another post** — I published more than one
|
|
2. **View calendar** — See remaining schedule → `/linkedin:calendar`
|
|
3. **Done** — All set for now
|
|
|
|
## Reference Files
|
|
|
|
- `${CLAUDE_PLUGIN_ROOT}/assets/drafts/queue.json`
|
|
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
|