workflow-contracts

Generate v1 handoff artifacts with required frontmatter for planning, review, or execution.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill workflow-contracts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-contracts
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/workflow-contracts
Command: npx skills add https://github.com/matt-riley/agent-skills --skill workflow-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill provides a standardized way to produce durable, structured handoff artifacts for planning, review, or execution, replacing ad-hoc chats with reproducible records.

Core Features & Use Cases

  • Supports three v1 artifact templates (planner handoff, review outcome, execution record) to capture goals, evidence, changes, and blockers.
  • Enforces stable frontmatter, headings, and validation steps to ensure artifacts are machine-checkable and future-proof.
  • Useful for teams needing explicit decisions, traceability, and handoffs across planning, review, and execution phases.

Quick Start

Create the appropriate v1 artifact by selecting a template from assets and populating the required frontmatter fields (contract_type, contract_version, created_by, status, plus the template-specific fields) to generate a ready-to-run artifact.

Frequently Asked Questions about workflow-contracts

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

FAQPage Schema
How do I create structured handoff artifacts for planning and execution workflows?▼

Create structured handoff artifacts by selecting a v1 template from assets and populating required frontmatter fields like contract_type, contract_version, and status to generate machine-parseable records for formal workflow handoffs.

What are durable workflow contracts and when do I need them?▼

Durable workflow contracts are structured artifacts replacing ad-hoc chats with reproducible records. You need them when teams require explicit decisions, traceability, and safe handoffs across planning, review, and execution phases.

Can I use machine-parseable handoff records for team planning and review phases?▼

Yes, machine-parseable handoff records support team planning and review phases. The skill enforces stable frontmatter, headings, and validation steps ensuring artifacts are machine-checkable and future-proof across all phases.

What's the best way to formalize execution records and review outcomes instead of ad-hoc chats?▼

Formalize execution records and review outcomes using v1 artifact templates that capture goals, evidence, changes, and blockers while enforcing stable frontmatter and clear next actions for reproducible team records.

Do I need specific frontmatter fields to generate valid workflow handoff artifacts?▼

Yes, valid workflow handoff artifacts require specific frontmatter fields including contract_type, contract_version, created_by, and status, plus additional template-specific fields depending on the artifact type selected.

Why does my handoff artifact fail validation during the execution phase?▼

Handoff artifact validation fails when required frontmatter fields like contract_type, contract_version, created_by, or status are missing, or when template-specific fields for goals, evidence, changes, and blockers are incomplete.