playbook-dev

Plugin playbook-dev from marketplace tgvashworth-agent-plugins in tgvashworth/agent-plugins. Commands read from the repo's manifest — 9 days ago.

Skills (22)

• aggregation-stage

  This skill should be used when the user asks to "design Stage 2", "create clustering analysis", "define aggregation axes", "build cohort analysis", "design cross-cluster synthesis", or needs to author the pattern identification stage.

• architecture-doc

  This skill should be used when the user asks to "document system architecture", "describe domain structure", "map system components", "create architecture reference", or needs to document the domain system being analyzed by the playbook.

• attribution-framework

  This skill should be used when the user asks to "build attribution framework", "establish causal attribution", "design change impact analysis", "create attribution chains", "trace cause to effect", or needs to establish causal links between changes and outcomes in playbook analysis.

• bi-directional-enrichment

  This skill should be used when the user asks to "design cross-stage enrichment", "create bi-directional updates", "enrich earlier outputs", "link later findings to earlier analysis", "update Stage 1 from Stage 3", or needs patterns for later stages to enrich earlier stage outputs.

• clustering-strategy

  This skill should be used when the user asks to "define clustering strategy", "create multi-axis clustering", "design cohort segmentation", "build clustering dimensions", "group items by multiple factors", or needs to design how items should be grouped across multiple dimensions.

• create

  Create a new multi-stage analysis playbook with the guided wizard. Use when the user invokes /playbook-dev:create, says "create a playbook", "build an analysis playbook", or asks to scaffold a new LLM analysis pipeline for a domain.

• finalization-stage

  This skill should be used when the user asks to "design Stage 4", "create executive summary", "define institutional memory", "build summary template", "design knowledge capture", or needs to author the finalization stage.

• glossary-creator

  This skill should be used when the user asks to "create glossary", "define metrics", "document terminology", "build term definitions", "define domain concepts", or needs to create standardized definitions for playbook analysis.

• impact-estimation

  This skill should be used when the user asks to "estimate impact", "design confidence framework", "create impact scoring", "define confidence levels", "build ROI analysis", or needs frameworks for estimating improvement impact in playbook analysis.

• master-instructions

  This skill should be used when the user asks to "write instructions.md", "create master orchestration", "define stage sequencing", "configure agent counts", "set operational constraints", or needs to author the main playbook instructions file.

• meta-analysis

  This skill should be used when the user asks to "create self-assessment", "build meta-analysis", "track playbook issues", "design theme-based analysis", "identify analysis process problems", or needs structures for analyzing the analysis process itself.

• per-item-stage

  This skill should be used when the user asks to "design Stage 1", "create per-item analysis", "define parallel analysis", "configure sub-agent prompts", "set up rolling pipeline", or needs to author the parallel per-item analysis stage.

• playbook-scaffold

  This skill should be used when the user asks to "create playbook directory structure", "scaffold a playbook", "set up playbook folders", "initialize playbook directories", or needs the initial file/folder layout for a new playbook.

• playbook-validator

  Validates playbook structure, completeness, and quality. Use when the user completes a stage, asks to validate, finishes major sections, or is ready to test a playbook.

• playbook-wizard

  This skill should be used when the user asks to "create a playbook", "build an analysis playbook", "design a multi-stage workflow", "set up an LLM analysis pipeline", or uses the /playbook-dev:create command. Provides guided, step-by-step playbook creation orchestrating all other playbook-dev skills

• quality-gates

  This skill should be used when the user asks to "define quality gates", "create exit criteria", "design validation steps", "set up stage prerequisites", "define completion criteria", or needs to establish quality checkpoints between playbook stages.

• setup-stage

  This skill should be used when the user asks to "design Stage 0", "create preflight checks", "define environment validation", "create scope document", "set up data validation", or needs to author the interactive setup stage of a playbook.

• stage-document

  This skill should be used when the user asks to "write a stage README", "create analysis document", "follow stage document format", "structure stage instructions", or needs guidance on the standard format for stage and analysis documents.

• synthesis-stage

  This skill should be used when the user asks to "design Stage 3", "create opportunity analysis", "define synthesis vectors", "build change impact analysis", "design improvement recommendations", or needs to author the cross-cutting insights stage.

• taxonomy-builder

  This skill should be used when the user asks to "create classification system", "build taxonomy", "define failure tags", "design classification tags", "create mutually exclusive categories", or needs to build machine-readable classification systems for playbook analysis.

• template-designer

  This skill should be used when the user asks to "create output template", "design analysis template", "define output format", "build document template", "structure output with placeholders", or needs to author standardized templates for playbook outputs.

• verification-script

  This skill should be used when the user asks to "create verification script", "build completion checker", "generate validation script", "check stage completion", "verify output files", or needs scripts to validate playbook outputs.

Subagents (1)

• playbook-validator

  Validates playbook structure, completeness, and quality. Triggers proactively when user completes a stage, says "validate", or finishes major sections.

Similar plugins