31 tagged loop, measured the same way as everything else here.
Browse within: ai-assistant 13ai-loops 12loop-engineering 12
Skill Claude CodeCodex
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
Skill Claude CodeCodex
A task-loop procedure that combines task recognition, planning, assignment, checking, handoffs, and a mock architecture-analysis step.
Skill Claude CodeCodex
Personal Chief of Staff system for ADHD-ish operators. Vault-based, loop-driven, nervous-system-aware. Built and lived-in across daily sessions on real consulting, content, and long-running personal work.
Skill Claude CodeCodex
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…
Skill Claude CodeCodex
The operating model for delivering product work items end-to-end with an agent harness. Use whenever working a ticket/issue under the-loop — to write the spec chain (requirements/design/testing-plan/tasks), execute the task DAG, verify against the testing plan, self/critic-review, escalate, present evidence, and…
Skill Claude CodeCodex
How the-loop writes for a human reader. Use when authoring or revising any artifact a person will read — requirements.md, design.md, testing-plan.md, tasks.md, a PR briefing or PR description, a decision record, a capability doc, a ticket or review comment, a README. Carries the document spine, the prefer-a-diagram…
Skill Claude CodeCodex
Full-cycle delivery method for Maestro sessions — Analysis and Plan when a task is created, then Development and Testing, then a conventionally-named branch and Conventional Commit. Use when planning a task draft or driving a worker task from start to pull request.
Skill Claude CodeCodex
Catalog of the Maestro maestro CLI: spawning workers, managing sessions and projects, sending messages, previewing pages, and daemon control. Use when using the to CLI, spawning workers, or managing Maestro sessions in an Maestro workspace.
Skill Claude CodeCodex
Triage bugs reported in chat/issues, search for duplicates, file or update GitHub issues with full context, and push fix PRs.
Skill Claude CodeCodex
Loop Engineering — a fully autonomous long-horizon engineering closed loop. Propose an idea → rough plan → run the entire project automatically (auto-selecting the best option at each decision point), only calling the user for verification at the end. Cross-tool orchestration of gstack (review) / OpenSpec (write) /…
Skill Claude CodeCodex
Loop Engineering — a fully autonomous long-horizon engineering closed loop. Propose an idea → rough plan → run the entire project automatically (auto-selecting the best option at each decision point), only calling the user for verification at the end. Cross-tool orchestration of gstack (review) / OpenSpec (write) /…
Skill Claude CodeCodex
Loop Engineering — a fully autonomous long-horizon engineering closed loop (degraded version for Gemini CLI / Codebuddy). Propose an idea → rough plan → run the project. Cross-tool orchestration of gstack / OpenSpec / GSD / Superpowers with adversarial quality gates. NOTE: interactive features (AskUserQuestion…
Skill Claude CodeCodex
Keep an interactive Codex CLI session working at a fixed interval by holding one active turn open and waiting on the input-interruptible clock.sleep tool between iterations. Use when the user invokes Loop, asks Codex to repeat or continue work at an interval while the terminal session stays open, or wants a running…
Skill Claude CodeCodex
Stop the active Loop in this Codex CLI session — stop re-arming clock.sleep and close out the turn the loop was running in. Use ONLY when the user explicitly asks to stop, end, kill, or cancel the loop. Never invoke this on your own initiative while a loop is running.