Quick Reference
Purpose
The Crew Roles skill defines seven specialized coordination roles that orchestrate multi-persona collaboration for comprehensive, high-quality content generation when using Crew mode.
Seven Crew Roles
Creative Director:
- Oversees overall content vision and narrative arc
- Final decisions on structure and approach
- Ensures consistent story despite multi-voice contributions
Research Analyst:
- Verifies technical accuracy and source reliability
- Provides data and evidence for claims
- Fact-checks all persona contributions
Lead Writer:
- Coordinates persona assignments to sections
- Maintains style consistency across multiple voices
- Handles transitions between persona switches
Technical Reviewer:
- Validates code examples and technical details
- Ensures accuracy of implementation guidance
- Verifies architecture recommendations
Reader Advocate:
- Represents the target audience perspective
- Points out confusing sections or knowledge gaps
- Ensures accessibility appropriate to audience level
Devil's Advocate:
- Challenges assumptions and conventional thinking
- Identifies potential counterarguments
- Strengthens content by forcing deeper justification
Editor-in-Chief:
- Performs final quality review
- Enforces adherence to writing standards
- Makes publication decisions
When to Use Crew Roles
When to Use Crew Roles:
- When content spans multiple technical domains
- When quality requires cross-validation from multiple perspectives
- When collaborating as a team on a single comprehensive document
- High-stakes content requiring rigorous review
When to Skip Crew Roles:
- When simple solo mode content is sufficient
- When time constraints do not allow for coordination overhead
- When the topic would not benefit from multiple expert perspectives
Implementation Guide
Creative Director Role
The Creative Director provides strategic oversight to ensure all persona contributions contribute to a unified content vision.
Responsibilities:
Setting the Vision:
- Define content goals and target outcomes
- Establish narrative structure and flow
- Determine appropriate tone and style
- Approval of persona assignments by section
Quality assurance:
- Reviewing vision alignment of completed sections
- Identifying content coverage gaps
- Requesting revisions when sections miss the goal
- Ensuring a consistent whole emerges from the parts
Decision authority:
- Final decision-making authority on structural changes
- Approval of persona assignments
- Resolving conflicts between roles
- Determining publication readiness
Typical assignment:
- Often handled by the analyst or architect persona
- Requires big-picture thinking and analytical skills
- Benefits from an authoritative tone for decision-making
Research analyst role
The research analyst ensures that all factual claims are accurate, sourced, and reliable.
Responsibilities:
Source verification:
- Verifying the accuracy and recency of all cited sources
- Checking that URLs are valid and return relevant content
- Verifying statistics and benchmarks against authoritative sources
- Pointing out unsupported claims that require evidence
Technical fact-checking:
- Checking technical details against official documentation
- Verifying version numbers and release dates
- Verifying API signatures and code syntax
- Cross-referencing multiple sources for contentious claims
Citation management:
- Ensuring proper citation formatting throughout
- Checking that reference numbers match citations
- Editing the complete references section
- Tracking source metadata for all materials
Typical assignment:
- The analyst persona fits naturally (data-driven, analytical)
- The reviewer persona also fits (balanced evaluation)
- Requires systematic attention to detail
Lead writer role
The lead writer ensures stylistic consistency and smooth transitions and coordinates multi-persona collaboration.
Responsibilities:
Section assignment:
- Mapping content sections to appropriate personas
- Matching areas of expertise to content needs
- Balancing workload across personas
- Creating assignment specifications with clear boundaries
Transition management:
- Designing explicit transition markers between sections
- Writing bridging sentences that connect voices
- Maintaining narrative flow despite voice changes
- Ensuring reader comprehension across transitions
Style consistency:
- Enforcing writing standards across all personas
- Ensuring consistent terminology usage
- Maintaining an appropriate level of formality
- Verifying citation style uniformity
Typical assignment:
- The mentor persona fits (educational coordination)
- The developer persona also fits (practical organization)
- Strong understanding of all persona voices required
Technical Reviewer role
The technical reviewer verifies all technical content for accuracy and completeness.
Responsibilities:
Code review:
- Ensure all code examples run correctly
- Syntax checking for the target language/framework version
- Ensure examples follow best practices
- Test that the code demonstrates the claimed behavior
Technical accuracy:
- Verify that architectural patterns are explained correctly
- Confirm the accuracy of system design principles
- Ensure framework usage matches the documentation
- Verify that configuration examples work
Implementation guidance:
- Ensure step-by-step instructions are complete
- Verify commands and setup procedures
- Ensure tutorials lead to the expected results
- Point out missing dependencies or prerequisite knowledge
General assignment:
- Developer persona is ideal (hands-on validation)
- Architect persona also suitable (design validation)
- Reviewer persona also suitable (systematic evaluation)
Reader Advocate role
The reader advocate represents the target audience to ensure the content fits their needs and level of understanding.
Responsibilities:
Accessibility check:
- Point out sections that are too advanced for the target audience
- Identify assumed knowledge that is not explained
- Request clarification for confusing explanations
- Ensure jargon is defined on first use
Flow validation:
- Check the logical progression of concepts
- Identify knowledge gaps in the explanation
- Verify that examples match the difficulty level
- Point out complexity jumps without scaffolding
User experience:
- Ensure the content delivers the promised value
- Verify the practical applicability of the guidance
- Ensure examples are relevant to real-world use cases
- Ensure key points are clear and actionable
General assignment:
- Mentor persona is a perfect fit (learner-focused)
- Developer persona also suitable (practical empathy)
- Requires understanding of the target reader's background
Devil's Advocate role
The devil's advocate challenges the content from a critical perspective, strengthening the argument through counterarguments.
Responsibilities:
Challenge assumptions:
- Question assumptions not stated in the content
- Identify potential counterarguments
- Challenge the conventional wisdom presented
- Force deeper justification for claims
Identify edge cases:
- Point out scenarios where the advice does not apply
- Identify the limitations of the recommended approach
- Pointing out potential pitfalls or drawbacks
- Ensure warnings and precautions are included
Alternative perspectives:
- Suggest contrarian perspectives to address
- Identify missing perspectives
- Challenge one-sided presentations
- Strengthen content by enforcing completeness
General assignment:
- Columnist persona fits naturally (critical thinking)
- Reviewer persona's critical perspective also fits
- Requires a skeptical and questioning mindset
Editor-in-chief role
The editor-in-chief performs a final quality gate review before approving publication.
Responsibilities:
Standards compliance:
- Ensure all writing standards are met
- Ensure AI-prevention patterns are removed
- Ensure citation completeness
- Verify formatting consistency
Quality review:
- Evaluate overall content quality
- Check for typos and grammar issues
- Verify logical flow and consistency
- Ensure value delivery aligns with goals
Publication decision:
- Decide final publication approval
- Request revisions if quality is insufficient
- Approve content for publication
- Sign off on completed work
General assignment:
- Curator persona fits (quality-focused)
- Analyst persona also fits (systematic review)
- Requires high standards and attention to detail
Advanced patterns
Role assignment strategy
Persona-role mapping:
Analyst persona:
- Optimal roles: Creative Director, Research Analyst, Editor-in-Chief
- Strengths: systematic thinking, data-driven, objective evaluation
Architect persona:
- Optimal roles: Creative Director, Technical Reviewer
- Strengths: big-picture vision, technical depth, design validation
Developer persona:
- Optimal roles: Lead Writer, Technical Reviewer, Leader Advocate
- Strengths: practical focus, hands-on validation, accessibility
Mentor persona:
- Optimal roles: Lead Writer, Leader Advocate
- Strengths: educational focus, learner empathy, clear communication
Reviewer persona:
- Optimal roles: Technical Reviewer, Research Analyst, Devil's Advocate
- Strengths: balanced evaluation, systematic review, critical thinking
Columnist persona:
- Optimal roles: Devil's Advocate, Creative Director
- Strengths: critical perspective, challenging thinking, strong opinions
Curator persona:
- Optimal roles: Editor-in-Chief, Research Analyst
- Strengths: quality focus, fact-checking, standards enforcement
Role coordination workflow
General Crew Mode Workflow:
Step 1 - Planning (led by Creative Director):
- Define content vision and goals
- Establish structure and section classification
- Assign personas to sections (coordinated by Lead Writer)
- Set quality standards and requirements
Step 2 - Research (led by Research Analyst):
- Gather sources and verify reliability
- Compile research briefs for writers
- Verify technical claims and data
- Prepare citation base
Step 3 - Writing (coordinated by Lead Writer):
- Personas write assigned sections
- Technical Reviewer verifies code/technical content
- Reader Advocate points out accessibility issues
- Devil's Advocate challenges assumptions
Step 4 - Review (led by Editor-in-Chief):
- Verify compliance with standards
- Review quality across all sections
- Final fact-checking pass
- Approve publication or request revisions
Role Communication Patterns
Clear Communication Requirements:
From Creative Director:
- Vision statements must be specific and measurable
- Structural decisions documented with rationale
- Revision requests include clear success criteria
From Research Analyst:
- Flagged issues include proposed sources for resolution
- Fact-check reports cite authoritative alternatives
- All verification results documented with evidence
From Lead Writer:
- Section assignments clearly specify scope boundaries
- Transition requirements communicated explicitly
- Style guidance provided before writing
From Technical Reviewer:
- Technical issues explained with specific examples
- Provide proposed fixes, not just issue identification
- Clearly indicate verification status (approved/needs revision)
From Reader Advocate:
- Identify confusion points with specific examples
- Provide improvement suggestions
- Explicitly state the target audience perspective
From Devil's Advocate:
- Challenges must be constructive, not mere criticism
- Alternative perspectives supported with reasoning
- Provide suggestions for addressing counterarguments
From Editor-in-Chief:
- Quality decisions clearly justified
- Revision requests specific and actionable
- Approval signature explicit and final
Things That Work Well Together
Skills:
- protocols - provides the crew mode framework in which roles operate
- personas - provides the 8 unique personas assigned to roles
- writing-standards - the quality framework reinforced by the editor role
- research - protocol used by the research analyst role
Command:
- post - when the post command uses crew mode, the crew role coordinates
Quality standards
Role execution requirements
Each role must comply with the following:
- Stay within the defined scope of responsibility
- Communicate findings clearly
- Provide actionable feedback
- Respect the authority of other roles
- Collaborate toward shared quality goals
Cross-role verification
Final content must satisfy the following:
- Creative director: vision and structure aligned
- Research analyst: all facts verified and sourced
- Lead writer: style consistency maintained
- Technical reviewer: all technical content accurate
- Reader advocate: accessibility appropriate for the audience
- Devil's advocate: major challenges addressed
- Editor-in-chief: all quality standards met
Version: 2.0.0 Last Updated: 2026-01-06 Category: Collaboration Framework Type: Role Definitions Status: Production Ready