skills.rest
tacogips
tacogipsCOMMUNITY
Explore all skills by this author →
𝕏@yu_kawa_tacoGitHub

divedra-workflow

Author and validate divedra workflow bundles with step-addressed workflow.json files.

1|Updated Nov 9, 2024
Search Tags:#validation#JSON schema#workflow authoring#portable bundles#manager worker routing#cross-workflow transitions
One-click install
npx skills add https://github.com/tacogips/ign --skill divedra-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: divedra-workflow
Source: https://github.com/tacogips/ign/tree/main/.agents/skills/divedra-workflow
Command: npx skills add https://github.com/tacogips/ign --skill divedra-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes ambiguity and schema errors when authoring divedra workflow bundles, so your workflows validate against the current implementation.

Core Features & Use Cases

  • Portable workflow authoring: Create step-addressed bundles with workflow-relative node and prompt paths.
  • Schema-first validation guidance: Validate step graphs, node payloads, transitions, and add-ons using the divedra CLI (or Bun script) described in the skill.
  • Correct composition patterns: Structure workflows using a reusable node registry and clean steps[].transitions instead of legacy routing fields.

Quick Start

Generate and validate a portable workflow bundle by authoring workflow-root/workflow-name/workflow.json plus any needed nodes/node-<id>.json and prompts/*.md, then run the divedra workflow validation command.

Frequently Asked Questions about divedra-workflow

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

FAQPage Schema
How do I validate a portable workflow bundle before deployment?▼

To validate a portable workflow bundle, run the divedra workflow validation command using the --workflow-root flag and the workflow name to check step-addressed graphs, node payloads, and prompt files against the current schema.

What is a step-addressed workflow.json graph and when do I need it?▼

A step-addressed workflow.json graph defines execution paths using workflow-relative node and prompt paths. You need it when authoring portable bundles that require reliable manager/worker routing and cross-workflow transitions.

How do I structure transitions correctly when authoring JSON workflow schemas?▼

Structure workflow transitions by using clean steps[].transitions arrays within your workflow.json instead of legacy routing fields. This approach ensures correct composition patterns and passes schema-first validation.

Why does my workflow validation fail with schema errors on node payload files?▼

Workflow validation fails when node payload files and prompt files do not match the step-addressed workflow.json graph. Ensure all node-<id>.json files and prompts use workflow-relative paths aligning with the reference format.

Can I use a reusable node registry for cross-workflow transitions in portable bundles?▼

Yes, you can use a reusable node registry to structure workflows with clean transitions for cross-workflow transitions. The bundle validates correctly when nodes reference the registry and follow the provided workflow format reference.

Related Skills

Explore More Software Engineering Skills→
campbellmcgregorcampbellmcgregor

agentic-development

Guide AI-assisted software builds with workflows, model selection, and prompt strategies.

Community
Basic
ZTE-AICloudZTE-AICloud
52

sdd

Route feature requests into a spec-driven development workflow with optional workflow modes.

Official
Advanced
arestivoarestivo

openspec-continue-change

Generate the next OpenSpec change artifact from CLI status and instructions.

Community
Advanced
jonnymuirjonnymuir
1

workflow-editor-copy-paste

Standardize copy and paste operations across workflow editor surfaces.

Community
Intermediate