protocols

Writing Protocols

Quick Reference

Purpose

The Writing Protocols skill defines three modes for coordinating persona-based content generation that enable flexible workflow selection based on content complexity and requirements.

Three Writing Modes

Solo Mode:

A single persona writes the entire document
Maintains a consistent voice
Best for: Simple topics with clear persona fit
Fastest execution, highest consistency

Crew Mode:

Multiple personas collaborate on a single document
Each handles specific sections according to their expertise
Best for: Comprehensive content requiring diverse perspectives
Highest quality, deepest coverage

Adaptive Mode:

A single persona switches context mid-document
Switches between technical depth and accessibility
Best for: Mixed audience knowledge levels, mixed content types
Balanced approach, flexible adaptation

Mode Selection Guide

When to choose Solo Mode:

When the topic fits precisely within a single persona's domain
When a consistent voice is important for document cohesion
When time constraints require the fastest execution
Example: Pure implementation tutorial → Developer persona

When to choose Crew Mode:

When the topic spans multiple domains requiring different expertise
When different perspectives improve understanding
When quality and depth take priority over speed
Example: Full-stack architecture guide → Architect + Developer + Reviewer

When to choose Adaptive Mode:

When the audience has mixed knowledge levels
When content alternates between concepts and implementation
When a single voice is needed but context switching is required
Example: Beginner tutorial with advanced sections → Mentor adjusting tone

Implementation Guide

Solo Mode Protocol

Solo mode assigns the entire document to a single optimal persona while maintaining a consistent voice.

Selection Process:

Step 1 - Analyze Content Domain:

Identify the main topic category
Determine expertise requirements
Assess target audience level

Step 2 - Match Persona to Domain:

Technical Deep Dive:

Architecture patterns, system design → Architect
Implementation details, code examples → Developer
Technical comparison, frameworks → reviewer or analyst

Educational content:

Getting started guide, basics → mentor
Best practices for beginners → mentor or developer
Concept explanation → mentor

Personal/narrative content:

Memoir, lessons learned → storyteller
Career journey, experience → storyteller or developer
Project chronicle → storyteller

Opinion/analysis content:

Industry commentary, trends → columnist or analyst
Technical criticism → columnist or reviewer
Controversial topics → columnist

News/update content:

Release notes, changelog → curator
Weekly roundup, news → curator or analyst

Step 3 - Execute as persona:

Apply the persona's trait combination throughout
Maintain consistent voice patterns
Use persona-specific reasoning approaches
Keep tone characteristics uniform

Quality standards:

No voice inconsistency
Trait markers appear consistently
Vocabulary matches the persona domain
Perspective is maintained consistently

Crew mode protocol

Crew mode coordinates multiple personas with defined section assignments and explicit transition markers.

Planning process:

Step 1 - Analyze content structure:

Identify the main sections of the planned content
Determine the expertise required for each section
Map concepts to persona strengths

Step 2 - Map personas by section:

Introduction section:

Overview and motivation → analyst or mentor
Problem statement → critical perspective of a columnist or architect

Architecture/design section:

System design, patterns → architect
Component relationships → architect
Scalability considerations → architect

Implementation section:

Code examples, practical steps → developer
Framework usage → developer
Tool configuration → developer or reviewer

Analysis section:

Performance metrics, benchmarks → analyst or reviewer
Alternative comparison → reviewer or analyst
Trade-off evaluation → architect or reviewer

Best practices section:

Recommendations for beginners → mentor
Common pitfalls → developer or storyteller
Learning roadmap → mentor

Conclusion section:

Summary and key points → original introduction persona
Future implications → analyst or columnist

Step 3 - Design transitions:

Explicitly mark section boundaries
Use clear headers for persona transitions
Maintain logical flow between sections
Preserve the overall narrative arc

Step 4 - Crew Coordination:

Each persona writes the assigned section
Maintain persona fidelity within sections
Respect transition points
Ensure overall consistency despite voice changes

Quality Standards:

Clear section boundaries
Smooth logical transitions
Each persona remains within their domain
Maintain overall narrative coherence

Adaptive Mode Protocol

Adaptive mode allows a single persona to adjust intensity and approach as needed across content subsections.

Adaptive Patterns:

Pattern 1 - Depth Variation:

Main persona maintains consistent voice patterns
Adjust technical depth without changing tone
Example: A developer switches from beginner to intermediate depth while maintaining a conversational voice

Pattern 2 - Perspective Shift:

Single area of expertise, diverse reasoning approaches
Example: A reviewer alternates between analytical data and experiential anecdotes while maintaining a balanced evaluative tone

Pattern 3 - Tone Adjustment:

Adjust emotional register for different section types
Example: A mentor starts nurturing in the fundamentals, then becomes more authoritative with advanced concepts

Implementation Guidelines:

When to Adapt:

When moving from concept explanation to implementation details
When transitioning between beginner and advanced sections
When shifting from objective analysis to practical recommendations
When changing from problem description to solution proposal

How to Signal Adaptation:

Use subsection headers that mark contextual shifts
Brief transitional sentences that prepare the reader
Example: "Now that we understand the basic concepts, let's look at the actual implementation"

What to Maintain:

Core voice patterns (formal vs polite style)
Overall area of expertise
Reader relationship (as the writer being expert/mentor/colleague)

What Can Change:

Technical depth and vocabulary complexity
Evidence type (theoretical vs practical)
Level of abstraction (patterns vs details)
Example complexity (simple vs production-grade)

Quality Standards:

Adaptation feels natural and not awkward
Core persona identity remains recognizable throughout
Transitions are explicitly marked
Adjustments contribute to content needs

Advanced Patterns

Cross-Mode Strategies

Hybrid Solo-Adaptive:

Start with a single persona in solo mode
Switch to adaptive in specific difficult sections
Return to pure solo in the conclusion
Use case: One complex subsection within mostly simple content

Sequential Crew:

Uses crew mode but personas write sequentially rather than in parallel
Each persona builds on the previous persona's work
Maintains a stronger narrative flow than parallel crews
Use case: A tutorial series where each step requires different expertise

Crew with Adaptive Lead:

Uses crew mode with section assignments
Each assigned persona uses adaptation within their own section
Combines the advantages of specialized expertise and flexibility
Use case: A comprehensive guide with varying depth across multiple domains

Mode Selection Decision Tree

Simple Decision Flow:

Question 1: Does the topic clearly fit within one persona domain?

Yes: Consider solo mode
No: Consider crew or adaptive mode

Question 2: Does the content require multiple distinct perspectives?

Yes: Choose crew mode
No: Continue evaluation

Question 3: Does the content require varying depth within the same domain?

Yes: Choose adaptive mode
No: Choose solo mode

Question 4: Is execution speed important?

Yes: Solo mode (fastest)
No: Crew mode (highest quality)

Quality Verification by Mode

Solo Mode Verification:

Single persona identity is maintained throughout
No unintended voice switching
Consistent trait application
Persona selection appropriate for the topic

Crew Mode Verification:

Clear section boundaries with explicit markers
Each section matches its assigned persona
Logical flow between sections
Consistent overall narrative despite the multi-voice approach

Adaptive Mode Verification:

Adaptation contributes to clear content needs
Transitions are explicitly signaled
Core persona identity remains recognizable
Adjustments enhance rather than confuse

Things That Work Well Together

Skills:

personas - Provides 8 unique personas coordinated by the protocol
traits - Defines the combination components that personas combine
writing-standards - A quality framework applied across all modes
crew-roles - Defines specialized roles for crew mode coordination

Commands:

post - Use the protocol for workflow decisions for content generation

Mode Examples

Solo Mode Example

Topic: "React Hooks Practical Guide" Selected persona: Developer (conversational voice, implementation expertise, experiential perspective)

The entire document is written in a conversational haeyo-che style with personal anecdotes and provides practical examples of hook usage. A consistent developer voice from introduction to conclusion.

Crew Mode Example

Topic: "The Complete Guide to Microservices Architecture"

Section Assignments:

Introduction + Problem Statement: Architect (formal, analytical, authoritative)
Architectural Design Principles: Architect
Service Implementation: Developer (conversational, practical, empathetic)
Performance Analysis: Analyst (formal, data-driven, authoritative)
Common Pitfalls: Storyteller (narrative, experiential, empathetic)
Conclusion: Architect

Each section contributes to a cohesive whole while maintaining a distinct voice.

Adaptation Mode Example

Topic: "TypeScript Migration for Beginners" Selected Persona: Mentor (default nurturing tone)

Adaptation:

Foundations Section: Highly nurturing, simple examples
Type System Section: More analytical, increased technical depth
Advanced Patterns: Authoritative tone, complex examples
Troubleshooting: Returns to nurturing, empathetic support

The same mentor persona is maintained throughout, preserving its core identity while adjusting its approach according to content needs.

Version: 2.0.0 Last Updated: 2026-01-06 Category: Content Creation Type: Workflow Orchestration Status: Production Ready