Consulting Content Drafter

Workspace: use the selected project and its AGENTS.md; keep existing entity folders and Reality headings. Business paths below are relative to that project. Bundled resources are relative to this installed skill; sibling capabilities resolve by their installed names. Never search another private checkout for missing inputs. Use workspace identity, audience, pricing, and DESIGN.md fonts.

Steps

1. Take the signal (from signals/) — read its source/related and traverse to the raw for context.
2. Ground research-derived drafts (pull the wiki). If the idea cites [[wiki pages]] (it came from recoup-internal-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.
3. Choose a clear title naming the subject and reader benefit. Use numbers only when supported; no mandatory headline formula.
4. Choose the structure that fits the material: essay, briefing, demonstration, interview or Q&A. AIDA is optional. A newsletter can include industry interpretation, useful product developments, field notes and reader questions without forcing every item into a sales case study.
5. Place it on the specificity ladder (generic → category → specific → targeted) and match it to the business stage.
6. Save the draft to content/03-drafts/ with a clear title; note the target audience (IC vs. leadership).