autowork

Coordinate single-owner task workflows through implementation, verification, and closure.

20.1k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill autowork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autowork
Source: https://github.com/kortix-ai/suna/tree/main/core/kortix-master/opencode/skills/KORTIX-workflows/autowork
Command: npx skills add https://github.com/kortix-ai/suna --skill autowork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the coordination of a single owner across task implementation, verification, and finalization, reducing handoffs and errors.

Core Features & Use Cases

  • Persistent single-owner task loop with strict verification gates
  • Reads contextual artifacts from .kortix/docs/ to guide execution
  • Provides clear completion criteria and evidence-based claims

Quick Start

Initialize and run a persistent autowork loop for a single owner, tracking tasks and emitting verified completion only when results are proven.

Frequently Asked Questions about autowork

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

FAQPage Schema
How do I automate end-to-end task execution with strict verification?

Automate end-to-end task execution by running a persistent single-owner loop that guides work through implementation and verification gates, emitting completion only after results are proven.

What is a single-owner task workflow with strict verification gates?

A single-owner task workflow is an orchestration loop where one owner manages execution to completion, passing strict verification gates before finalizing to reduce handoffs and errors.

How do I start a persistent task loop that reads context from .kortix/docs?

Start a persistent task loop by initializing the workflow, which then reads contextual artifacts from .kortix/docs/ to guide execution and enforce evidence-based completion claims.

Does task orchestration work without external dependencies?

Task orchestration runs without external dependencies, using a change-tolerant context reading mechanism to guide the persistent loop from start to verified completion.

Why use a single-owner task loop over standard task-management workflows?

Use a single-owner task loop to eliminate handoffs and errors, ensuring one owner strictly guides implementation through verification gates before claiming final completion.

When should I not use a single-owner task loop for orchestration?

Avoid a single-owner task loop for orchestration scenarios requiring multi-owner collaboration or distributed execution, as it strictly enforces a single owner across the entire task lifecycle.