workflow-contract

Coordinate multi-agent workflows by producing structured workflow status reports.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/mkrlabs/specflow --skill workflow-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-contract
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/workflow-contract
Command: npx skills add https://github.com/mkrlabs/specflow --skill workflow-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates coordinated work across multiple agents by standardizing reporting with a machine-readable workflow status.

Core Features & Use Cases

  • Structured WORKFLOW STATUS blocks emitted at the end of each phase to enable downstream agents to act.
  • Clear handoff targets (e.g., developer, QA, review) to guide task progression and auditing.
  • Audit-friendly reporting with blockers, next actions, and validation results to improve traceability.

Quick Start

Coordinate a multi-agent session by preloading a structured workflow status contract into all participants.

Frequently Asked Questions about workflow-contract

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

FAQPage Schema
How do I coordinate multi-agent workflows with clear handoffs between roles?

You coordinate multi-agent workflows by mandating structured status reports at the end of each phase, ensuring clear handoffs and traceability across manager, developer, QA, and review roles.

What is a structured workflow status block and when do I need it for agent coordination?

A structured workflow status block is a machine-readable report emitted after task execution phases. You need it when orchestrating multiple agents to enforce consistency, state semantics, and downstream actionability.

How do I audit multi-agent task execution and track blockers across handoffs?

You audit multi-agent execution by reviewing structured status reports that capture validation results, blockers, and next actions, providing complete traceability for every coordinated task progression.

Can I use structured workflow status reporting for QA and developer role coordination?

Yes, structured workflow status reporting explicitly supports QA and developer role coordination by defining clear handoff targets, state semantics, and mandated status blocks to guide task progression.

What's the best way to standardize reporting across multiple agents in a coordinated session?

The best way to standardize reporting is preloading a structured workflow status contract into all participating agents, enforcing consistent machine-readable outputs, handoff targets, and audit-friendly reporting.

Why does my multi-agent workflow lose context during role transitions?

Multi-agent workflows lose context during role transitions without structured handoff targets and mandated status blocks, which are required to enforce state semantics and ensure downstream agents can act.