workflow-reference

Translate RFC normative language into formal Ivy constructs and run verification.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/ElNiak/panther-ivy-plugin --skill workflow-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-reference
Source: https://github.com/ElNiak/panther-ivy-plugin/tree/main/plugins/panther-ivy-plugin/skills/workflow-reference
Command: npx skills add https://github.com/ElNiak/panther-ivy-plugin --skill workflow-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating complex RFC specifications into formal Ivy code, verifying protocol implementations, and ensuring adherence to quality standards.

Core Features & Use Cases

  • RFC to Ivy Mapping: Provides patterns and guidance for converting normative RFC language into testable Ivy assertions and state machines.
  • Verification Workflow: Details how to run Ivy verification using MCP tools and interpret common failure modes for debugging.
  • Quality Gates: Outlines the automated pipeline for evaluating specification quality across structural correctness, type safety, semantics, and RFC traceability.
  • Use Case: A protocol engineer needs to formally specify a new feature defined in an RFC. They use this Skill to understand how to map the RFC's requirements into Ivy code, run verification to catch errors early, and ensure their specification meets the project's quality bar.

Quick Start

Use the workflow-reference skill to understand how to map RFC requirements into Ivy constructs.

Frequently Asked Questions about workflow-reference

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

FAQPage Schema
How do I translate RFC normative language into formal Ivy constructs?

To translate RFC normative language into formal Ivy constructs, you map protocol requirements into testable Ivy assertions and state machines using established mapping patterns. This ensures the original specification logic is accurately formalized for verification.

How does formal verification work for protocol specifications using Ivy?

Formal verification for protocol specifications using Ivy works by running the ivy-tools MCP to check code against defined assertions. It evaluates structural correctness, type safety, semantics, and RFC traceability through automated quality gates.

What is the best way to interpret Ivy verification failure modes when debugging protocols?

The best way to interpret Ivy verification failure modes is to follow the verification workflow guidance, which maps common failure outputs back to their originating RFC requirements. This pinpoints whether the issue is structural, type safety, or semantic.

What quality checks are required for evaluating protocol specification quality?

Evaluating protocol specification quality requires automated quality gates checking four dimensions: structural correctness, type safety, semantics, and RFC traceability. This pipeline ensures the formal Ivy code accurately reflects the original RFC.

Do I need ivy-tools MCP to run formal verification on RFC specifications?

Yes, you need ivy-tools MCP to run formal verification on RFC specifications. The verification workflow specifically details how to execute checks using this MCP and interpret the resulting failure modes for protocol debugging.