skills.rest
shawnroos
shawnroosCOMMUNITY
Explore all skills by this author →
Website𝕏@shawnroosGitHub

auto-backend

Standardize custom backends for the auto loop engine with a strict interface.

Updated Jun 12, 2026
Search Tags:#automation#workflow#backend#auto#engine#loop
One-click install
npx skills add https://github.com/shawnroos/auto --skill auto-backend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-backend
Source: https://github.com/shawnroos/auto/tree/main/skills/auto-backend
Command: npx skills add https://github.com/shawnroos/auto --skill auto-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured framework for developers to create custom backends for the auto loop engine, ensuring that new workflows integrate seamlessly with the engine's fixed operational requirements.

Core Features & Use Cases

  • Standardized Interface: Implements the six required operations (plan, deepen, review_plan, next_plan_step, do_step, review) to drive the engine's plan and work loops.
  • Severity Mapping: Provides a clear mechanism to translate native workflow vocabulary into the engine's shared blocker/major/minor severity scale.
  • Use Case: Use this skill when you need to adapt a new toolchain or custom workflow logic to the auto engine, ensuring your backend satisfies the contract for state machine execution.

Quick Start

Follow the auto-backend guide to implement the six required operations and define your severity mapping table for a new workflow.

Frequently Asked Questions about auto-backend

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

FAQPage Schema
How do I build a custom workflow backend for the auto engine?▼

Build a custom workflow backend by implementing the six required plan and work operations—plan, deepen, review_plan, next_plan_step, do_step, and review—defined in the backend-contract.md specification.

What is the severity mapping logic required for an auto loop backend?▼

Severity mapping translates native workflow vocabulary into the auto engine's shared blocker, major, and minor severity scale. A three-tier severity translation logic is required to standardize execution state handling.

When do I need to implement a state-machine-driven execution backend?▼

Implement a state-machine-driven execution backend when adapting a new toolchain or custom workflow logic to the auto engine, requiring durable execution and strict operational interfaces for plan and work loops.

Does the auto engine backend contract require specific operations for workflow integration?▼

Yes, the backend contract requires six specific operations: plan, deepen, review_plan, next_plan_step, do_step, and review. Adherence to these operations facilitates durable state-machine execution.

What are the limitations of using a standardized interface for workflow backends?▼

The standardized interface requires strict adherence to the backend-contract.md specification and a three-tier severity translation logic, limiting flexibility for toolchains that cannot map to the plan and work loop operations.

Related Skills

Explore More Software Engineering Skills→
oalansilvaoalansilva

compliance-readiness

Identify policy gaps against required controls and generate a prioritized remediation plan.

Community
Intermediate
Azure-SamplesAzure-Samples
60

durable-functions-dotnet

Orchestrate Azure Functions workflows using the Durable Task Scheduler.

Official
Advanced
multicammulticam

Assembler Agent Pattern

Coordinate AI coding agents to execute work orders and integrate versioned code.

Community
Advanced
daudaudinangdaudaudinang

lp-implement

Execute LittlePea delivery loop from implement through QA after plan approval.

Community
Advanced