waza

Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication

Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication

Prepare and publish a new version of the waza azd extension. USE FOR: "publish extension", "release new version", "bump version", "prepare release", "update changelog", "azd publish", "new release", "version bump", "cut a release". DO NOT USE FOR: running evals (use waza), writing skills (use skill-authoring), CI/CD pipeline changes (edit workflow files directly).

**UTILITY SKILL** - Explain code snippets, functions, and algorithms in plain language. USE FOR: explain code, what does this code do, break down this function, help me understand this, walk through this algorithm, clarify this logic, explain this snippet, describe what happens here. DO NOT USE FOR: writing new code (use code generation), fixing bugs (use debugging), refactoring (use refactoring skills), code review with action items. INVOKES: file reading tools to access code, language detection for tailored explanations. FOR SINGLE OPERATIONS: If the user just needs to see file contents, use file reading tools directly.

Explains code snippets in plain English, breaking down what the code does step by step. Perfect for learning, code reviews, or documentation.

The complete two-phase Init Mode protocol the Squad coordinator runs when no team exists yet in the current repo. Phase 1 = propose the team (no files created, wait for user confirm). Phase 2 = create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins (Scribe, Ralph, Rai, Fact Checker). Loaded on demand when the coordinator detects no .squad/team.md exists.

Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode. This skill contains the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules. Squad coordinator loads this on demand once routing has identified the agent — to pick the right ceremony level for the task.

The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece of state belongs, or answer a 'who owns this file' question.

Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.

Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories

Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.

Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.

Squad branching model: dev-first workflow with insiders preview channel

Squad branching model: dev-first workflow with insiders preview channel

Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation. Use when spawning sub-agents to complete scoped work.

**WORKFLOW SKILL** - Process PDF files including text extraction, rotation, and merging. USE FOR: "extract PDF text", "rotate PDF", "merge PDFs", "split PDF pages", "convert PDF to text". DO NOT USE FOR: creating PDFs from scratch (use document-creator), editing PDF forms (use form-filler). INVOKES: pdf-tools MCP for extraction, file-system for I/O. FOR SINGLE OPERATIONS: Use pdf-tools MCP directly for simple extractions.

Process PDF files including text extraction, rotation, and merging. USE FOR: "extract PDF text", "rotate PDF", "merge PDFs", "split PDF pages", "convert PDF to text". DO NOT USE FOR: creating PDFs from scratch (use document-creator), editing PDF forms (use form-filler).

Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.

Reviewer rejection workflow and strict lockout semantics

Never read .env files or write secrets to .squad/ committed files