formalize

Convert jam artifacts into event schemas, mocks, and validation configurations.

14|6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/tyevans/tackline --skill formalize
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: formalize
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/formalize
Command: npx skills add https://github.com/tyevans/tackline --skill formalize

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms human agreements documented in jam sessions into machine-readable event schemas, mocks, and validation configurations, bridging the gap between discussion and implementation.

Core Features & Use Cases

  • Event Schema Generation: Creates versioned YAML schemas for owned events based on jam artifacts.
  • Mock & Stub Creation: Generates mock producers for consumed events and stub consumers for owned events to facilitate local development.
  • Validation Configuration: Produces a validation.yaml file to enforce contract compliance for sprint agents.
  • Use Case: After a collaborative Event Storming session, use this Skill to automatically generate the formal event schemas and contract tests needed for developers to start building services that communicate reliably.

Quick Start

Use the formalize skill with the path to your jam artifact 'docs/jam/session-2023-10-27.md'.

Frequently Asked Questions about formalize

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

FAQPage Schema
How do I generate machine-readable event schemas from Event Storming jam artifacts?β–Ό

You generate machine-readable event schemas by parsing jam artifacts to extract event details, field definitions, and ownership. This process codifies human agreements into versioned YAML schemas for bounded contexts.

How do I create mock producers for consumed events in event-driven architecture?β–Ό

You create mock producers by formalizing consumed event agreements from jam artifacts into executable code. This generates mock producers and stub consumers to facilitate local development and reliable service communication.

What is the best way to enforce API design contracts for sprint agents?β–Ό

The best way to enforce API design contracts is by generating a validation.yaml configuration from jam artifacts. This file codifies field definitions and confidence levels to ensure contract compliance for sprint agents.

Can I formalize bounded context agreements without manual schema coding?β–Ό

Yes, you can formalize bounded context agreements without manual coding by parsing jam artifacts. The tool extracts field definitions and ownership to automatically generate versioned YAML schemas and validation configurations.

What limitations exist when codifying confidence levels from event storming sessions?β–Ό

Limitations exist if the source jam artifacts lack clearly defined event details, field definitions, or ownership data. Accurate schema generation and mock creation require parsing complete event storming agreements.

Do I need jam artifacts to generate event schemas and validation configurations?β–Ό

Yes, you need jam artifacts because they contain the human agreements required for formalization. The tool parses these artifacts to extract event details and confidence levels for schema generation and validation configuration.