Skill: ivangdavila/cycle (version 1.1.0)

--- name: Cycle description: Design custom workflow cycles for any domain. Create structured, repeatable processes that become persistent skills. --- ## 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 1. **Goal** — What does this cycle produce? Be specific. 2. **Map** — How does user currently do it? Where do they get stuck? 3. **Phases** — 3-6 sequential steps with clear input/output each 4. **Handoffs** — Automatic, gated (needs user), or conditional 5. **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.

path: discovery.md
content: # Discovery Questions

Ask before designing a cycle:

1. "What triggers this process?" (request, schedule, event)
2. "What does 'done' look like?"
3. "What steps do you always do?"
4. "What steps do you often skip but shouldn't?"
5. "Where do you spend the most time?"
6. "What decisions require your input vs. can be automated?"

## Red Flags

- Vague goals ("better results") → push for specifics
- Too many phases (>6) → likely multiple cycles
- No validation points → add checkpoints


path: examples.md
content: # Cycle Examples

## Writing Cycle

**Trigger:** Topic idea
**Done:** Published post with social snippets

```
Outline → Draft → Self-critique → Revise → SEO → Publish
```

Gates: Outline approval, final review before publish.

## Code Review Cycle

**Trigger:** PR opened
**Done:** Approved and merged

```
Understand → Test locally → Review → Comment → Re-review → Approve
```

Gates: At least one approval required.

## Research Cycle

**Trigger:** Question or topic
**Done:** Synthesized report with sources

```
Scope → Search → Filter → Analyze → Synthesize → Format
```

Gates: Scope confirmation, source quality check.


path: implementation.md
content: # Implementing Cycles

Cycles become skills with this structure:

```
cycle-name/
├── SKILL.md          # Main workflow (short)
├── phases/
│   ├── plan.md       # How to execute Plan
│   ├── execute.md    # How to execute Execute
│   └── verify.md     # How to execute Verify
└── state.md          # Persistent preferences
```

## SKILL.md Template

```markdown
---
name: [Cycle Name]
description: [What it produces]
---

## Workflow
[Phase] → [Phase] → [Phase] → [Phase]

## Phases
- **[Phase 1]** — [input] → [output]
- **[Phase 2]** — [input] → [output]
...

Read `phases/[name].md` for each phase details.
```

## State Persistence

The `state.md` file tracks:
- **Preferences** — User's style, tools, constraints
- **Patterns** — What works for this user
- **Never** — Things that consistently fail


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)