| name | consulting-content-drafter |
| description | Turn an idea or insight into a publish-ready draft. Use on "draft a post/blog about X", "write this up", or when promoting a signal from signals/. |
Consulting Content Drafter
Steps
- Take the signal (from
signals/) — read its source/related and traverse to the raw for context.
- Ground research-derived drafts (pull the wiki). If the idea cites
[[wiki pages]] (it came
from consulting-research-miner) or the topic is agent/skill/AI-engineering-shaped, follow
integrations/research/AGENTS.md to read the relevant whole wiki pages (incl. ## What we'd steal) and pull concrete, cited specifics to build the draft on — carry the [[citations]] so
every claim stays traceable. Out-of-domain topic? Skip this — the wiki is silent on generic
app/business, so don't force it.
- Apply the title formula: "[N] steps to [outcome] by [%] using [tool/method]"; prefer "you" over "I".
- Structure with AIDA (Attention → Interest → Desire → Action). Lead with the problem + outcome, not your resume.
- Place it on the specificity ladder (generic → category → specific → targeted) and match it to the business stage.
- Save the draft to
content/03-drafts/ with a clear title; note the target audience (IC vs. leadership).
Output: a draft ready for review. Sources: Ch. 5 + (for agent/skill topics) the research wiki via integrations/research/AGENTS.md.