workflow-blueprint

Scaffold modular route-based agent workflows with contracts and runbooks.

66|4|Updated May 6, 2026

Search Tags:#automation #documentation #routing #scaffolding #orchestration #workflows #contracts

Ready to run

npx skills add https://github.com/devton/agentic-workflow-blueprint --skill workflow-blueprint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-blueprint
Source: https://github.com/devton/agentic-workflow-blueprint/tree/main
Command: npx skills add https://github.com/devton/agentic-workflow-blueprint --skill workflow-blueprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the scaffolding of modular, route-based agent workflows and contracts.

Core Features & Use Cases

Executable workflow contracts (Goal, Scope, Triggers, Inputs, Invariants, Procedure, Outputs, Review gate, References) for each planned workflow.
Router-only command model: /<skillName> <cmd> maps to workflows/<cmd>/SKILL.md.
Automatic generation of project entry skill (SKILL.md) and template.json, plus reference routing matrices and runbooks.
Progressive disclosure: core details live behind links while root documentation stays concise.

Quick Start

Trigger the blueprint in your repository to scaffold skills/<projectSlug>/, with routing, references, and workflow contracts.

Frequently Asked Questions about workflow-blueprint

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

FAQPage Schema

How do I automate modular agent workflow scaffolding with deterministic routing?▼

Modular agent workflow scaffolding is automated by generating a router-only entry skill that maps commands to specific workflow contracts. This ensures deterministic routing, governance, and traceable execution across orchestrated agent tasks.

What are executable workflow contracts and how do they structure agent runbooks?▼

Executable workflow contracts define structured runbooks using elements like Goal, Scope, Triggers, Inputs, Invariants, Procedure, Outputs, and Review gates. They ensure deterministic execution and traceable governance for each modular agent workflow.

Can I use route-based command mapping for my existing agent repository?▼

Yes, route-based command mapping applies to any repository requiring an orchestrated entry skill. It automatically scaffolds routing matrices, template.json manifests, and linked runbooks for your project's specific workflows.

What is the best way to organize modular agent workflows without cluttering root documentation?▼

The best way to organize modular workflows is through progressive disclosure, keeping core details behind links while root documentation stays concise. This is achieved by scaffolding per-workflow contracts and references linked from a router-only entry skill.

Do I need to manually create template.json manifests when scaffolding agent workflows?▼

No, you do not need to manually create template.json manifests. The scaffolding process automatically generates the project entry skill, template.json manifests, reference routing matrices, and linked runbooks to satisfy workflow governance requirements.