Individual skill

task-cycle

Run the defect lifecycle for one resolved tracked task. Confirms matches, owns the defect ledger and linked evidence, runs bounded repair and verification, reopens safely, and closes when every gate passes and policy allows. New bug feedback enters through task-bug first.

plugins/agent-foundry/skills/task-cycle/SKILL.md

Read pinned source

Source commit e1a5a792f45899379b42c06e7a332ff40caa7c2f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
13
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Task Cycle

`task-cycle` is the canonical defect-lifecycle executor and the sole writer of
the managed defect ledger and linked defect records for a tracked task.
Use `$task-bug [<ID>] "<feedback>"` as the preferred user-facing intake for new
bug evidence; call `$task-cycle <ID>` directly to resume defects already in the
ledger. The cycle owns the task's managed defect ledger plus its linked defect
records and automatically continues safe same-task work; the operator must not
have to invoke `$implement-task` again.

Plain conversational feedback after an implementation or verification handoff
must enter through task-bug first. A defect ID supplied by conversation,
memory, summary, or router context is only a candidate until this cycle checks
the canonical ledger and linked record.