ワンクリックでManusで任意のスキルを実行

programmers-loop

スター0

フォーク0

更新日2026年7月13日 19:23

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

ParkerRex

ParkerRex/little-loop

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Programmers Loop

Run programmers-loop standup --github and repair failing prerequisites.
Read docs/contracts/assignment.md, program.md, and exec-plan.md.
Locate or create the owning Assignment.
Use a Program when research, convergence, or multiple ordered slices are required. Otherwise create a standalone ExecPlan.
Resolve immutable Program briefs once per child plan with program child-plan; keep its snapshot and receipt.
Preview proof commands, then write, lint, grill, execute, and validate each ExecPlan through the explicit-consent CLI phases.
Record decisions and discoveries in the durable document as they happen.
Refresh the Program after every completed slice; choose the next slice or complete it explicitly.
Run programmers-loop planning lint and $verify-programmers-loop before handoff.

Never treat chat history as the sole source of planning truth. Never execute commands from a plan without explicit authority and the configured safety boundary.

このリポジトリの他の Skills

同じリポジトリ

run-exec-plan

ParkerRex/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.

2026-07-140

run-program

ParkerRex/little-loop

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.

2026-07-140

workshop-system

ParkerRex/little-loop

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.

2026-07-130

diagnose-programmers-loop

ParkerRex/little-loop

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.

2026-07-130

maintain-docs-spine

ParkerRex/little-loop

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.

2026-07-130

plan-assignment

ParkerRex/little-loop

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.

2026-07-130

name	programmers-loop
description	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.

Programmers Loop

Run programmers-loop standup --github and repair failing prerequisites.
Read docs/contracts/assignment.md, program.md, and exec-plan.md.
Locate or create the owning Assignment.
Use a Program when research, convergence, or multiple ordered slices are required. Otherwise create a standalone ExecPlan.
Resolve immutable Program briefs once per child plan with program child-plan; keep its snapshot and receipt.
Preview proof commands, then write, lint, grill, execute, and validate each ExecPlan through the explicit-consent CLI phases.
Record decisions and discoveries in the durable document as they happen.
Refresh the Program after every completed slice; choose the next slice or complete it explicitly.
Run programmers-loop planning lint and $verify-programmers-loop before handoff.

Never treat chat history as the sole source of planning truth. Never execute commands from a plan without explicit authority and the configured safety boundary.