consultant-playbook

Coordinate expert teams through structured codebase research lifecycle workflows.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/lygav/vladi-plugins-marketplace --skill consultant-playbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consultant-playbook
Source: https://github.com/lygav/vladi-plugins-marketplace/tree/main/plugins/squad-archetype-consultant/team/skills/consultant-playbook
Command: npx skills add https://github.com/lygav/vladi-plugins-marketplace --skill consultant-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain expert teams require a disciplined, repeatable lifecycle to answer questions about codebases and specialized domains. The Consultant Playbook provides a structured workflow to charter teams, index knowledge, monitor progress, and deliver answers with consistent signals and learnings.

Core Features & Use Cases

  • Onboarding: initializes domain context, team charter, and initial configuration for rapid startup.
  • Indexing & Research: guides systematic analysis of codebases and documents to build a searchable knowledge base.
  • Ready & Researching loops: defines trigger-based interactions for questions, responses, outbox reports, and learning entries.
  • Signals & Learnings: standardizes inbox/outbox signals and stores learnings for future reference.
  • Milestones & Reporting: tracks progress through defined stages and artifacts to enable retrospective reviews.

Quick Start

Start by loading this playbook into your meta-squad environment and begin onboarding a new domain expert team.

Frequently Asked Questions about consultant-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage structured workflows for consultant teams answering codebase questions?

Consultant Playbook coordinates expert teams to execute structured lifecycle workflows for codebase questions. It charters teams, indexes knowledge, monitors progress, and delivers answers using consistent signals and learnings.

What is the best way to standardize onboarding and indexing for specialized domain teams across multiple projects?

Use a structured playbook to initialize domain context, team charters, and configurations for rapid startup. It guides systematic codebase analysis to build a searchable knowledge base consistently across projects.

How do inbox and outbox signals work for team-management workflows in software engineering?

Inbox and outbox signals standardize trigger-based interactions for questions, responses, and reports. They drive automation by defining clear milestones, outputs, and status transitions throughout the research loop.

Does this approach require a specific environment to operate effectively?

The playbook is designed for a meta-squad environment where consultant teams operate. It uses trigger keywords and configuration files to drive automation without external dependencies.

When do I need a repeatable lifecycle process for codebase research and Q&A?

You need this process when repeatedly onboarding teams, indexing codebases, and conducting research across multiple software engineering projects. It ensures consistent answers, learning logs, and retrospective reviews.

What limits or constraints exist when indexing knowledge with a structured team playbook?

The playbook applies specifically to software engineering domains requiring onboarding, indexing, research, and Q&A. It depends on defined trigger keywords and status transitions to drive automation effectively.