workflow

Routes software engineering tasks by risk classification and selects skills for implementation and proof.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/kreek/consult --skill workflow-kreek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/kreek/consult/tree/main/plugin/skills/workflow
Command: npx skills add https://github.com/kreek/consult --skill workflow-kreek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering tasks vary widely in risk, and treating a trivial config change like a database migration wastes time while treating a migration like a trivial change causes failures. This Skill classifies each task by significance and durability, then routes it to the right engineering skills and approval gates so ceremony scales with actual stakes. ## Core Features & Use Cases - Risk-Based Task Routing: Classifies work by significance (how much code it touches) and durability (how costly it is to reverse), then sets the appropriate human involvement level. - Skill Selection and Gating: Maps tasks to specialized skills (debugging, domain-modeling, security, proof, code-review, and more) and enforces sign-off gates only for durable shapes like interfaces, data models, and migrations. - Completion Loop with Proof: Requires every non-trivial change to be proven via tests or checks and pass a fresh-context code review before close-out. - Use Case: When asked to add a new API endpoint, the Skill routes the task through contract-first approval for the interface, domain-modeling for data shapes, and proof plus code-review before declaring the work done. ## Quick Start Use the workflow skill to plan and route this engineering task, naming its risk profile and the skills needed to complete it.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I decide which skills to load for a coding task?▼

Classify the task by significance and durability first, then load only skills that change the next action or proof obligation. The workflow provides a mapping table from task types like debugging, API design, or database changes to their corresponding skills.

How does risk-based task classification work for code changes?▼

Tasks are scored on significance (how much other code they impact) and durability (how costly they are to reverse). Low-stakes disposable work runs autonomously, while high-stakes work triggers approval gates before durable shapes are built.

When should approval gates be skipped in an engineering workflow?▼

Skip gates for trivial changes with no behavior, contract, data, or security risk, and for local helpers, private file moves, or narrow bug fixes restoring intended behavior. Gates apply only to durable shapes like interfaces, data models, migrations, and releases.

What happens when no human is available to approve a design decision?▼

Build the most conservative version of the gated shape, mark it provisional, and flag the decision in the close-out summary. Continue all work the gate does not block and state assumptions explicitly.

When should I not use a general workflow router for a task?▼

Skip it when a narrower skill is explicitly requested and fully covers the task, when the change is trivial with no risk surface, or for platform operations with no code, contract, or proof question.