---
name: writing-logic
description: Writing employee · Argument scaffolding system. Takes an idea (or a source) and sequences it into a Perspective-Shift scaffold — one protagonist's Old→New journey across labeled beats, one takeaway each, ordered to meet the reader where they are and break the idea down progressively. Build the scaffold, then QA it for logical integrity before any prose. USE WHEN user says 'plan argument', 'scaffold this', 'argument structure', 'plan the newsletter structure', 'sequence these ideas', 'logic check my writing', 'check my logic', 'expand this idea', 'map my ACTs', or when building the argument structure for any content piece before writing prose.
context: fork
agent: general-purpose
---

# writing-logic — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="writing-logic", path="SKILL.md", section="contents")`

The tool prefix varies by host. Search available and lazy-loaded tools for any name ending in `get_skill`. If none exists, run the local `check-setup` skill and follow its repair. Do not improvise install commands or versions, and never ask for a license key in chat.

Follow the returned routing map. Fetch only the section this run needs, then fetch each workflow, reference, template, example, or script it names with the same `skill_id` and exact remote path. Those files live on the AIEB server, not local disk. If a fetched instruction says to run a script, fetch it first and follow its safety instructions.

If the server returns a 🔒, entitlement, or setup message, relay its explanation and next action once. Do not retry a locked call, reconstruct paid content, or claim setup is fixed before a live fetch succeeds.