Skip to main content
Ejecuta cualquier Skill en Manus
con un clic
Repositorio de GitHub

looper

looper contiene 6 skills recopiladas de ajhcs, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.

skills recopiladas
6
Stars
1
actualizado
2026-07-12
Forks
0
Cobertura ocupacional
2 categorías ocupacionales · 100% clasificado
explorador de repositorios

Skills en este repositorio

looper
Desarrolladores de software

Write compact Codex orchestration loops over accepted plans, beads, implementation slices, review/fix passes, and selective subagents. Use when the user asks for a loop, agent loop, workflow loop, Codex loop, retry loop, evaluator loop, multi-agent loop, or orchestration prompt.

2026-07-12
looper
Desarrolladores de software

Write compact Codex orchestration loops over accepted plans, beads, implementation slices, review/fix passes, and selective subagents. Use when the user asks for a loop, agent loop, workflow loop, Codex loop, retry loop, evaluator loop, multi-agent loop, or orchestration prompt.

2026-07-12
beadwriter
Desarrolladores de software

Decompose parent beads, specs, plans, completed Wayfinder maps, and grill-with-docs output into evidence-backed, commit-sized childbeads with explicit execution packets. Use when the user asks to beadwrite, split work into atomic commits, prepare work for Looper, or turn planning artifacts into implementation units.

2026-07-11
system-mapper
Desarrolladores de software

Inspect, create, validate, render, and deepen System Understanding Maps from typed Map Sources before planning or implementation work.

2026-07-11
bead-cleaner
Otras ocupaciones informáticas

Audit open bd beads against the project's current direction and safely re-scope, defer, deduplicate, supersede, close, or delete them. Use when the user asks to clean up, prune, triage, archive, close, or delete stale, obsolete, duplicate, abandoned, or nonsensical beads.

2026-07-10
phone-a-swe
Desarrolladores de software

Phone-A-SWE researches software engineering decisions before implementation. Use when the user asks to phone a SWE, choose between technical options, evaluate a library/API/framework/MCP/skill, or ground a codebase decision in repository evidence and current primary sources.

2026-07-05