run-cycle

name	run-cycle
description	Choose a Knights Radiant cycle and hand-off sequence for greenfield, risky migration, triage, refactor, or small-task work.
category	knights-radiant

Run Cycle

Use this skill when the task needs not just one lens, but an intentional sequence of scrutiny.

run-cycle vs choose-order: choose-order picks the narrowest first lens for the immediate constraint. run-cycle picks a fuller sequence when the task needs multiple lenses in order. On the same task, they may recommend different starting orders — choose-order optimizes for "what matters most right now," run-cycle optimizes for "what sequence covers the full scope." That divergence is intentional, not a bug.

Inputs required

• task statement
• work type: greenfield, risky migration, triage, refactor, or ordinary small task
• known constraints, deadlines, and risk level

Procedure

1. Determine the work type:
   • greenfield feature or subsystem
   • risky migration or phased cutover
   • bug triage or incident response
   • refactor or cleanup
   • ordinary small task
2. Select the cycle from CYCLE.md.
3. Name the required hand-off artifact for the first order before starting.
4. Keep one active order at a time; the next order inherits the artifact, not a blank prompt.
5. Stop early when the minimum viable cycle is enough.

Output shape

Return a cycle packet with:

• selected cycle
• ordered list of active orders
• first baton owner
• required hand-off artifact for the current step
• stop condition for the cycle
• expected final deliverable

Default small-task triplet

Lightweaver → Skybreaker → Windrunner

Default risky migration cycle

Elsecaller → Bondsmith → Skybreaker → Windrunner

Example invocation

"Use run-cycle for: 'we have a flaky billing webhook, unclear root cause, and a hotfix window tomorrow morning.'"

Shared docs

Read CYCLE.md and IDEALS.md in this repo before running the cycle.