refactor(linkedin-studio): wire or delete 11 orphan agents (case-by-case) — 9 here, 2 in Steps 14/16
Resolves the orphan-agent audit finding by the locked default: wire all, no deletions, so the agent count stays 19. Per agent, added Task to the target command's allowed-tools and a coherent 'subagent_type: linkedin-studio:<name>' delegation at a real point in the command's flow (not a token grep-match). Wired (agents 1-9 of 11): video-scripter -> video.md (Step 4); content-optimizer -> post.md (Step 7 refinement) + ab-test.md (2a.4 optimized challenger); analytics-interpreter -> report.md (Step 7, report mode) + analyze.md (Step 2, interpret mode); content-planner -> batch.md (Step 2) + pipeline.md (Step 1); trend-spotter -> batch.md (Step 1) + pipeline.md (Step 1); network-builder -> outreach.md (Step 3a); strategy-advisor -> strategy.md (Step 3); voice-trainer -> setup.md (Step 3a); post-feedback-monitor -> calendar.md (publish action, 48h monitor). Deferred to their dedicated steps: #10 differentiation-checker -> Step 14 (short-form de-AI gate), #11 engagement-coach -> Step 16 (first-hour command). Namespaced subagent_type form requires a session reload before the wired agents are invokable. Verify: each of the 9 has >=1 invocation in commands/; structural lint 61/61 (counts 19/26/25/6 intact); agent-fixtures 35/35; hook tests 62/62. Three-doc + version reconciliation deferred to Step 21 per the locked plan [skip-docs]. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
c5b4c58f4f
commit
9f65daa288
11 changed files with 28 additions and 5 deletions
|
|
@ -46,6 +46,8 @@ Otherwise, check state file for `next_planned_topic`:
|
|||
1. I have an idea already
|
||||
2. Generate ideas for me
|
||||
|
||||
To situate the post in the broader plan — does it fill a content-mix gap or repeat a recent pillar? — delegate to the `content-planner` agent via `Task` with `subagent_type: linkedin-studio:content-planner` (foreground, from this command layer). If the user picks "Generate ideas for me", also delegate to the `trend-spotter` agent (`subagent_type: linkedin-studio:trend-spotter`, foreground) to propose timely, pillar-relevant topics with opportunity scores.
|
||||
|
||||
## Step 2: Draft
|
||||
|
||||
Once topic is chosen, create the draft:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue