protolabs

Start or stop protoLabs Studio auto-mode for autonomous feature processing. Agents automatically pick up backlog features respecting dependencies.

Activates AVA, your Autonomous Virtual Agency. Autonomous operator — identifies friction, ships fixes, keeps work flowing. Use for product direction, operational leadership, or when things need to get done.

View and manage the protoLabs Studio Kanban board. List features, check status, create new features, or review agent output.

Activates the Calendar Assistant. Manages all calendar operations including event creation, updates, scheduling, and deadline tracking. Use when you need to work with calendar data or schedule events.

Manage context files that are injected into AI agent prompts. Add coding standards, architectural guidelines, or project-specific rules.

Research codebase before planning a feature. Gathers context, identifies patterns, and documents constraints.

Validate approaches and question architectures with evidence-based research. Use when evaluating a technology choice, validating an approach, comparing solutions, or questioning an architectural decision.

Deep work mode - autonomously process features, merge PRs, groom the board, and stay productive until the system is void of work.

Analyze, critique, and improve prompts for LLM agents — system prompts, templates, or any instruction set.

Manage feature dependencies and execution order. Set up which features must complete before others can start.

Full project lifecycle — research, PRD, milestones, feature creation, and launch.

Promote code through the release pipeline (dev->staging->main). Handles version bumps automatically.

Activates Quinn, QA Engineer. Validates releases, runs regression checks, verifies service wiring, tests API endpoints, and generates pass/fail reports. Use when you need QA work, release verification, endpoint testing, wiring checks, or regression analysis. Invoke with /quinn or when user says "QA", "test the release", "verify", "regression", or discusses quality assurance.

Set up Langfuse tracing for Claude Code in the current project. Configures the Stop hook and environment variables so every conversation turn is traced.

Point at any repo — scan it, measure the gap against our gold standard, initialize automation, and create alignment work. The entry point for onboarding projects to protoLabs Studio. Accepts either a git URL or a local path.

Ship current changes — stage, commit, push, create PR, enable auto-merge. Handles conflicts automatically.

Create a SPARC-style Product Requirements Document for a feature or project.

Update the protoLabs Claude Code plugin to the current version. Handles uninstall, reinstall, env migration, and verification.

User onboarding — detect setup state, collect identity, orient to the board, create a first feature, and print a command reference card.

Review completed agent work and provide feedback or suggest improvements.

Analyze a codebase to understand structure, patterns, and suggest feature dependencies.

Codebase exploration agent for gathering context before planning.

Backup and restore Automaker Docker volumes.

Run comprehensive health diagnostics for Automaker deployment.

Analyze Automaker container logs for errors, patterns, and issues.

Creates features from project phases with proper dependencies.

Break down a complex feature into smaller, implementable tasks with proper dependencies.

PRD validation agent that checks quality and feasibility.

Creates project directory structure from approved PRD.

SPARC PRD creation agent for structured requirements documents.

14 hooks across 6 events