# Blog writing specialist Human Guide

## What This Is For
Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. It gives the agent a clearer input/output frame for content production: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Blog writing specialist agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for blog writing specialist.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Blog writing specialist guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Scattered thoughts and ideas
- Conversational yet substantive
- Mix of short and long sentences
- Specific examples and real details
- Is there a journey from one understanding to another?
- Can you identify a problem and resolution?
- Does it follow: comfort → disruption → return changed?
- Problem/experience → Journey → Results → Lessons
- Setup → Challenge → Discovery → Application
- Philosophy → How-to → Reflection
- Current state → Past → Learning → Future
- Hook with current position or recent event

## Decision Points And Nuance
The original skill emphasizes: Workspace Context, Operating Contract, Quick Decision Tree, Post Types, Tutorial / How-To, Deep Dive / Explainer, Postmortem / Incident Report, Benchmark / Comparison, Architecture / System Design, Writing Rules for Developers.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- | List prerequisites explicitly | Don't waste wrong audience time |
- ❌ "Obviously..." (if obvious, don't write it)
- | Every code block must be runnable | Broken examples destroy trust |
- Don't require organization. The mess is the input.
- Don't try to be clever - just state what they said
- **Code examples**: Required for Technology posts
- Every draft MUST include:
- "That week, I learned to code with my eyes wide shut. The strange part? I've never seen more clearly where we're headed."

## Copy-And-Paste Prompt
```text
Use the Blog writing specialist human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the manojbajaj95/claude-gtm-plugin skill entry for `blog-writing-specialist`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Blog Writing Specialist

## Workspace Context

Read bootstrap context before asking questions: `strategy/brand.md` for brand, audience, offer, channels, tools, constraints, and metrics; `about/me.md` for personal voice; `content/ideas.md` and `content/calendar.md` for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to `content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md`, and route durable learnings back to `strategy/brand.md`, `about/me.md`, or `content/ideas.md`.

## Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.


Comprehensive blog writing combining technical depth, personal voice transformation, and AEO optimization.

## Quick Decision Tree

Default to the user's workspace voice from `about/me.md`. Use the named legacy voices below only when the user explicitly asks for that voice or the bundled reference files clearly apply to the current project.

| Input Type | Use Section |
|-----------|-------------|
| Technical tutorial, deep dive, benchmark | Technical Blog Writing |
| Brain dump → polished post | Technical Blog Writing + workspace voice, or Nick Nisi Voice only when requested |
| Personal voice request | `about/me.md` by default, or Jarad's Voice only when requested |
| Company/product/technology category post | Category System adapted to `strategy/brand.md` |
| Not sure | Start here, adapt as needed |

---

# Part 1: Technical Blog Writing

Write developer-focused technical blog posts.

## Post Types

### 1. Tutorial / How-To

Step-by-step instruction. Reader should build something.

```
Structure:
1. What we're building (with screenshot/demo)
2. Prerequisites
3. Step 1: Setup
4. Step 2: Core implementation
5. Step 3: ...
6. Complete code (GitHub link)
7. Next steps / extensions
```

| Rule | Why |
|------|-----|
| Show the end result first | Reader knows if worth continuing |
| List prerequisites explicitly | Don't waste wrong audience time |
| Every code block should be runnable | Copy-paste-run is the test |
| Explain the "why" not just the "how" | Tutorials that explain reasoning get shared |
| Include error handling | Real code has errors |
| Link to complete code repo | Reference after tutorial |

### 2. Deep Dive / Explainer

Explains a concept, technology, or architecture decision in depth.

```
Structure:
1. What is [concept] and why should you care?
2. How it works (simplified mental model)
3. How it works (detailed mechanics)
4. Real-world example
5. Trade-offs and when NOT to use it
6. Further reading
```

### 3. Postmortem / Incident Report

Describes what went wrong, why, and what was fixed.

```
Structure:
1. Summary (what happened, impact, duration)
2. Timeline of events
3. Root cause analysis