Equilio Loop

Use Loop as a Supporting Skill for adaptive orchestration. Preserve Frame → Map → Explore → Build → Integrate as the progression of concerns, not a required pipeline. Apply the Development Principles. Install Loop with all five Core Skills; invoke the selected skill or read and follow its current instructions: Frame, Map, Explore, Build, Integrate. Keep Loop and its dependencies from the same source revision. Report a missing dependency rather than substituting remembered instructions or fetching an unrelated latest version.

Establish current understanding

Use the work-artifact contract throughout, reusing current guidance already in context. Read the latest owning artifact at the start; it holds discoveries within a skill as well as between skills.

Inspect the goal, branch, project conventions, and existing work before creating anything. Reuse the artifact that owns the goal, or prepare a local Markdown artifact while establishing the project's shared destination. For broader work, use the delivery-slicing guidance to select a useful outcome linked to project-level understanding. Sequence by value and release dependencies, not merely by build-task order; revisit boundaries when mapping or prototype evidence changes them. Avoid duplicates and speculative delivery breakdowns.

Assess the five coordinates and relevant evidence under the shared routing guidance. Treat them as judgment lenses, not gates or scores; routing must work without hidden conversation state.

Choose, run, and reassess

Assess understanding → choose useful skill → run it → reconcile work artifact → reassess.

Use the next-operation guidance. Honor an explicitly requested skill first, skip satisfied concerns, and revisit only when new evidence materially requires it. Give the selected skill the goal, shared artifact, and relevant evidence; let its current instructions determine method and depth.

For a handoff to another agent or authorized multi-agent work, follow the agent-continuation guidance. Keep assignments bounded and artifact write-back owned by one active writer; inspect returned evidence and reconcile contradictions before routing from it. Parallel assignments do not redefine delivery boundaries; readiness depends on verifying the functioning slice.