virtual-team

Document a bug report with reproduction steps, severity, and expected behavior. Use when the user explicitly requests the Virtual Team bug workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Quiz the developer on technical decisions in the current work. Use when the user explicitly requests the Virtual Team check workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Create clean, atomic git commits following project conventions. Use when the user explicitly requests the Virtual Team commit workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Extract, define, and validate API contracts as concrete schema files. Use when the user explicitly requests the Virtual Team contracts workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Investigate a bug, reproduce it, trace the code, and document the root cause. Use when the user explicitly requests the Virtual Team debug workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Query project conventions and architectural decisions with source references. Use when the user explicitly requests the Virtual Team decisions workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Create setup guides, configuration references, runbooks, and operational documentation. Use when the user explicitly requests the Virtual Team docs workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Audit stack.md against available skills and report coverage gaps. Use when the user explicitly requests the Virtual Team doctor workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Define a cross-repository product initiative and shared agreements. Use when the user explicitly requests the Virtual Team epic workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Turn a rough feature idea into an actionable specification and stories. Use when the user explicitly requests the Virtual Team feature workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Run the internal bug-fix pipeline used by the flow workflow. Use when the user explicitly requests the Virtual Team flow-fix-pipeline workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Run the complete feature or bug-fix pipeline from specification through pull request. Use when the user explicitly requests the Virtual Team flow workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Stress-test a feature specification or plan before implementation. Use when the user explicitly requests the Virtual Team grill workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Capture session state for a clean transfer to another session. Use when the user explicitly requests the Virtual Team handoff workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Capture and refine a product idea through a structured interview. Use when the user explicitly requests the Virtual Team idea workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Execute an approved technical plan with TDD and verification. Use when the user explicitly requests the Virtual Team implement workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Create a detailed technical implementation plan from an approved feature. Use when the user explicitly requests the Virtual Team plan workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Prepare and create a pull request with testing and implementation notes. Use when the user explicitly requests the Virtual Team pr workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Create a business proposal from an idea or feature breakdown. Use when the user explicitly requests the Virtual Team proposal workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Revisit and sharpen an existing idea, specification, or plan. Use when the user explicitly requests the Virtual Team refine workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Investigate a market, technical, or codebase question with sourced evidence. Use when the user explicitly requests the Virtual Team research workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Review current changes for correctness, security, patterns, and acceptance criteria. Use when the user explicitly requests the Virtual Team review workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Initialize a repository with stack definition, documentation, and team conventions. Use when the user explicitly requests the Virtual Team start workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Summarize project state, backlog health, blockers, and next work. Use when the user explicitly requests the Virtual Team status workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Assess architecture, technical debt, dependencies, patterns, and risks. Use when the user explicitly requests the Virtual Team tech-review workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Check the installed Virtual Team version and explain how to update it. Use when the user explicitly requests the Virtual Team update-workflow workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Compare a feature specification against its implementation and report gaps. Use when the user explicitly requests the Virtual Team validate workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Create, remove, or inspect Git worktrees safely. Use when the user explicitly requests the Virtual Team worktree workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Run the Virtual Team flow in automatic mode while preserving verification gates. Use when the user explicitly requests the Virtual Team yolo workflow or when this workflow is the next stage of an active Virtual Team pipeline.

Use when editing client-facing IDEA and PROPOSAL prose — reframes loss-framed phrases as gain-framed and enforces section-aware verb tense rules

Use when starting any session — maps contexts to behavioral skills that should be active

File-based backlog implementation using docs/backlog.md (bracket markers). Default when stack.md has backlog local or no backlog field.

Abstract backlog operations interface. Load this skill before any backlog read/write operation — it defines the operations that all commands reference, delegating to the active implementation (local or external).

Go-specific patterns for dependency injection, interface design, testing with mockery, and idiomatic project structure.

Use when creating, reviewing, or referencing architectural decision records — defines the ADR format, three-gate creation threshold, and local/hub flavors

Use when evaluating architecture in tech-review — provides formal vocabulary (Depth, Seam, Leverage, Locality, Adapter, Pass-through) with diagnostic heuristics that produce precise, falsifiable findings instead of generic descriptions

External service backlog implementation (GitHub Issues, Linear, JIRA). Used when stack.md has backlog external with a backlog_config section.

Checkpoint protocol for resuming multi-phase commands after session interruptions

Use when writing production code — enforces dependency inversion and testable design through checkpoint questions before writing function signatures and constructors

Use when a consumer project has a CONTEXT.md file — defines the domain glossary convention for consistent terminology across specs, plans, and code. Pipeline commands read CONTEXT.md during context loading and use its vocabulary in generated artifacts.