little-loop

Write, lint, grill, execute, repair, and validate one Programmers Loop ExecPlan. Use when a bounded implementation slice needs self-contained context and deterministic acceptance commands.

Advance a Programmers Loop Program from evidence through convergence, immutable planning briefs, ordered ExecPlan slices, refresh, and completion. Use for initiatives too ambiguous or large for one ExecPlan.

Operate durable Assignment, Program, and ExecPlan loops in repositories using Programmers Loop. Use for ambiguous multi-slice work that needs checked-in decisions, bounded execution, critique, recovery, and deterministic acceptance.

Shape an ambiguous coding-system request before creating Programmers Loop artifacts. Use when scope, source of truth, dependencies, failure modes, proof, or the choice between a Program and one ExecPlan is still unclear.

Diagnose local and GitHub health for a Programmers Loop repository. Use for missing tools, invalid packets, broken configuration, agent availability, authentication, remote setup, or lifecycle drift.

Maintain the Programmers Loop documentation spine and Markdown quality contract. Use when adding, moving, linking, or revising repository docs, prompt routes, skill routes, architecture pages, or planning guidance.

Create or update a Programmers Loop Assignment packet. Use when one coherent body of work needs durable scope, shared evidence, Programs, standalone ExecPlans, or lifecycle status.

Produce a read-only Programmers Loop standup from active Assignments, Programs, ExecPlans, and doctor checks. Use for status, handoff, lifecycle drift, blockers, or local and GitHub health review.

Verify Programmers Loop changes with focused checks, aggregate proof, and honest failure reporting. Use before handoff, completion, commit, release, or after changing code, docs, prompts, skills, or planning artifacts.