loop

Detect artifact state and route feature workflows through review, implementation, audit, and fixes.

4|Updated Mar 23, 2025
One-click install
npx skills add https://github.com/matochu/pythia --skill loop-matochu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop
Source: https://github.com/matochu/pythia/tree/main/.agents/skills/loop
Command: npx skills add https://github.com/matochu/pythia --skill loop-matochu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate the full plan loop by detecting artifact state and routing through review, implementation, audit, and follow-up steps using subagents.

Core Features & Use Cases

  • Auto-detects current lifecycle state from artifact files (plans, reviews, implementations, audits) and routes to the next required action.
  • Supports multi-round workflows (review, implement, audit, fix, plan-fix, re-plan) with clear escalation paths and iteration tracking.
  • Coordinates with specialized subagents to execute each phase, ensuring separation of concerns and robust validation before progressing.

Quick Start

Invoke /loop to auto-detect the current artifact state and route to the next workflow step

Frequently Asked Questions about loop

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

FAQPage Schema
How do I automate an end-to-end feature workflow with review and audit steps?

Automated feature workflow orchestration routes through review, implementation, audit, and fixes by detecting artifact states. It uses subagents to execute each phase and validates workflow documents before progressing to the next step.

How does artifact state detection work for routing software implementation tasks?

Artifact state detection reads plan, review, implementation, and audit files deterministically. Based on the current lifecycle state found in these artifacts, the workflow routes the task to the next required development action automatically.

Can I use subagents to separate concerns during code review and implementation?

Subagent handoffs coordinate specialized agents to execute isolated workflow phases like review and implementation. This separation ensures robust validation occurs at each step before the orchestration loop progresses to subsequent tasks.

What is the best way to handle multi-round planning and fixing workflows?

Multi-round workflows support iterative cycles of review, implement, audit, fix, and re-plan. The orchestration loop tracks iterations and provides clear escalation paths to resolve issues across multiple development rounds.

Do I need explicit feature references to start the workflow loop?

Explicit feature or plan references are supported but not required. The workflow can auto-detect the current lifecycle state directly from existing artifact files to determine and route the next required action.

Why does my workflow not progress after an audit step?

Workflow progression halts after an audit if workflow-doc validation fails. The orchestration loop requires deterministic state reading of artifact files to confirm validation before routing to fixes or subsequent phases.