A Cycle is a structured workflow optimized for a specific goal, with clearly defined phases, inputs/outputs, and memory to become a persistent skill.

How is a Cycle different from a Loop?

A Cycle arranges distinct phases in sequence to produce a complete output, while a Loop repeats a single action. Cycles can include loops inside phases to handle iterative steps.

How do I start designing a Cycle?

Define the Goal, map the current process, design 3–6 phases with inputs/outputs, specify handoffs and memory, then validate and iterate. Use the discovery/implementation prompts to guide questions.

Cycle

Verified

@ivangdavila

npx machina-cli add skill @ivangdavila/cycle --openclaw

Files (1)

SKILL.md

1.6 KB

What is a Cycle?

A structured workflow optimized for a specific goal. Examples:

code — Request → Plan → Execute → Verify → Deliver
research — Question → Search → Synthesize → Report
content — Idea → Draft → Critique → Refine → Publish

When to Propose

User repeats similar multi-step processes
Current workflow has inefficiencies or skipped steps
User asks "how should I approach X every time?"

Design Process

Goal — What does this cycle produce? Be specific.
Map — How does user currently do it? Where do they get stuck?
Phases — 3-6 sequential steps with clear input/output each
Handoffs — Automatic, gated (needs user), or conditional
Memory — Preferences, patterns, things to avoid

Check discovery.md for questions to ask users when designing.

Phase Structure

Each phase needs: clear input → output, validation before proceeding, can delegate to sub-agent.

Check implementation.md for how to structure cycle skills.

Cycle vs Loop

Cycle	Loop
Different phases in sequence	Same action repeated
Produces complete output	Refines until criteria
Design once, use many times	Created per task

They combine: cycles can use loops within phases. Check examples.md for cycle patterns.

Related: For iterating until success criteria are met (same action repeated), see the loop skill.

Source

git clone https://clawhub.ai/ivangdavila/cycleView on GitHub

Overview

Cycle lets you build structured workflows optimized for a specific goal. It emphasizes clear phases, inputs/outputs, handoffs, and memory so processes become persistent skills.

How This Skill Works

Start with a specific Goal, map the current process, and design 3–6 sequential phases with defined inputs, outputs, and validation. Each phase can delegate to sub-agents; cycles may include loops within phases to handle iterative tasks.

When to Use It

User repeats similar multi-step processes
Current workflow has inefficiencies or skipped steps
User asks how should I approach X every time
Need consistent delivery across different domains or projects
When you want a process that remains a persistent skill over time

Quick Start

Step 1: Define the Goal and success criteria for the cycle.
Step 2: Map your current process and identify bottlenecks or skipped steps.
Step 3: Create 3–6 phases with clear input/output, handoffs, and a memory rule; plan validation before moving on.

Best Practices

Define a precise Goal with measurable outcomes
Map the current process and identify bottlenecks and gaps
Design 3–6 phases with clear input/output for each
Specify handoffs (automatic, gated, or conditional) and a memory of preferences
Validate thoroughly and iterate with feedback to refine phases

Example Use Cases

Code cycle: Request → Plan → Execute → Verify → Deliver
Research cycle: Question → Search → Synthesize → Report
Content cycle: Idea → Draft → Critique → Refine → Publish
Onboarding cycle: Gather requirements → Provision access → Guide first tasks → Review
Product/design pulse: Gather insight → Iterate prototype → Test → Refine → Release

Frequently Asked Questions

Add this skill to your agents