skills.rest
mvschwarz
mvschwarzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

development-team

Coordinate implementer, QA, and design roles into a single development loop.

60|9|Updated Apr 1, 2026
Search Tags:#design#development#collaboration#qa#gates#team-workflow#product-delivery
One-click install
npx skills add https://github.com/mvschwarz/openrig --skill development-team
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: development-team
Source: https://github.com/mvschwarz/openrig/tree/main/packages/daemon/specs/agents/shared/skills/pods/development-team
Command: npx skills add https://github.com/mvschwarz/openrig --skill development-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The development pod coordinates implementation, QA, and design to prevent gate-skipping and miscommunication, ensuring every feature passes through a consistent review process.

Core Features & Use Cases

  • Role alignment: aligns implementer, QA, and designer within a single development loop.
  • Gatekeeping: enforces documented acceptance criteria and reviews before changes proceed.
  • Proposal-based workflow: coordinates pre-edit proposals, feedback, and verification after changes.
  • End-to-end handoffs: provides structured handoffs from design to implementation to QA.

Quick Start

Boot the development pod workflow and coordinate implementer, QA, and design with a single rig command.

Frequently Asked Questions about development-team

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

FAQPage Schema
How do I coordinate cross-functional development teams without skipping QA gates?▼

Cross-functional development team coordination aligns implementer, QA, and designer roles within a single development loop to enforce documented acceptance criteria and prevent gate-skipping before changes proceed.

What is a proposal-based workflow for software product delivery?▼

A proposal-based workflow manages product delivery by coordinating pre-edit proposals, structured feedback, and post-change verification to ensure every feature passes through a consistent review process before merge.

How do I structure end-to-end handoffs from design to implementation to QA?▼

Structured end-to-end handoffs transition tasks sequentially from design through implementation to QA, ensuring each phase completes review requirements and validates changes before the next role begins processing.

Can I enforce acceptance criteria reviews before merging code changes?▼

Yes, gatekeeping mechanisms enforce documented acceptance criteria and mandatory reviews before code changes proceed, preventing miscommunication and ensuring every feature passes a consistent validation process.

What is the best way to orchestrate implementer, QA, and design roles in a unified playbook?▼

Role orchestration within a unified playbook aligns implementer, QA, and design roles into a single development loop, tracking proposals and structuring handoffs to satisfy cross-functional product delivery requirements.

Why does my development team workflow suffer from miscommunication during product delivery?▼

Development team workflows suffer miscommunication when gatekeeping is absent; enforcing a consistent review process with documented acceptance criteria and structured handoffs prevents miscommunication and ensures proper validation.

Related Skills

Explore More Software Engineering Skills→
bigeasyfreemanbigeasyfreeman
2

codegen-context

Construct coding prompts for AI agents from task specifications and verification contracts.

Community
Advanced
FxHollowFxHollow

land-and-deploy

Automate PR merge, CI wait, deployment, and canary verification workflows.

Community
Advanced
baasith6baasith6

creating-pr

Automate structured pull request creation with titles, descriptions, issue links, and reviewers.

Community
Intermediate
grigbgrigb
4

project-coordinator

Redirect deprecated project coordination tasks to the Project Manager agent.

Community
Basic