---
title: "contract-testing-flywheel"
description: "Generates a structured onboarding backlog that takes a team from zero to publishing verified consumer and provider contract tests on PactFlow, in Jira, GitHub Issues/Projects, or Azure DevOps, or as a manual markdown exp"
canonical: https://agentpluginsdirectory.com/plugins/contract-testing-flywheel
last-updated: 2026-09-28
---

# contract-testing-flywheel
Generates a structured onboarding backlog that takes a team from zero to publishing verified consumer and provider contract tests on PactFlow, in Jira, GitHub Issues/Projects, or Azure DevOps, or as a manual markdown export. Modelled on the Contract Testing Flywheel: Planning → Requirements → Design → Implementation → Testing → Deployment → Lessons-Learned, plus an optional management dashboard.
- Slug: contract-testing-flywheel
- Publisher: SmartBear Platform
- Repository: https://github.com/pactflow/pactflow-agent-skills
- Manifest: plugins/contract-testing-flywheel/plugin.json
- Version: 0.1.0
- Category (editorial): testing
- Skills: 1 (contract-testing-flywheel)
- MCP servers: 0
- Stars: 6
- Repository created: 2026-02-12
- Repository last pushed: 2026-09-28
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/contract-testing-flywheel
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What contract-testing-flywheel does, in the publisher's words

Takes a development team from zero to publishing both consumer and provider contract tests on PactFlow, by generating a structured onboarding backlog modelled on the Contract Testing Flywheel: Planning → Requirements → Design → Implementation → Testing → Deployment → Lessons-Learned, with an optional management dashboard.

PactFlow is the target broker: it's what hosts pacticipants, runs can-i-deploy, surfaces the cross-contract matrix, and (for BDCT) drives provider-contract verification via Drift. The plugin is language-, CI-, and team-agnostic; it's also scrum-tool-agnostic: it drives Jira, GitHub Issues/Projects, or Azure DevOps directly if one is connected, or renders the whole backlog as a markdown export you can import into anything else. Everything else (stack, CI tool, repos, notification channel, even the project/workspace identifier) is asked at runtime and parametrised into the templates.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/pactflow/pactflow-agent-skills/HEAD/plugins/contract-testing-flywheel/README.md

## Skills

- contract-testing-flywheel: Generate a structured onboarding backlog, in Jira, GitHub Issues/Projects, Azure DevOps, or as a manual markdown export, that drives a development team from zero to publishing both consumer and provider contract tests. Use when the user invokes /contract-testing-flywheel or asks to "kick off cont…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.