feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command

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>

hooks/prompts/post-creation-automation.md

@@ -0,0 +1,32 @@
+LINKEDIN POST-CREATION AUTOMATION: If a LinkedIn content file was just written (post draft, article, or content — NOT config, state, scripts, or docs), perform these post-processing steps:
+
+**1. Generate Alternative Hooks**
+Create 3 alternative hooks for the content just written. Present them as:
+```
+Alternative hooks:
+1. [hook 1] (X chars)
+2. [hook 2] (X chars)
+3. [hook 3] (X chars)
+```
+
+**2. Suggest Optimal Posting Time**
+Based on the day of the week, suggest the next optimal posting window:
+- Tuesday-Thursday: 8-9 AM or 12-1 PM CET (best)
+- Monday/Friday: 9-10 AM CET (good)
+- Weekend: 10-11 AM CET (lower reach but less competition)
+
+**3. 5x5x5 Engagement Reminder**
+Remind: 'Before posting, spend 15-20 minutes on 5x5x5 pre-engagement: find 5 people with overlapping audiences, comment thoughtfully on their recent posts.'
+
+**4. Content Logging**
+Note: The post topic and hook should be logged to the state file when the session ends (handled by Stop hook).
+
+**5. Voice Sample Suggestion**
+
+After generating alternative hooks and posting time, add a brief note:
+
+"Tip: Your post hook could become a voice sample. When the session ends, the Stop hook will ask if you'd like to save it to your voice profile."
+
+This creates awareness of the voice extraction feature without interrupting the post-creation flow.
+
+**Skip this** if the file written is a config file, state file (.local.md), script, hook, JSON, plan file, or documentation.