speclisted
Install: claude install-skill william-london/ownframework-loop
# OwnFramework Loop - spec
This skill is a host adapter over the deterministic ofloop core.
## Rules
- Never approve your own packet.
- Never write STATE.json, APPROVAL.json, REVIEW_VERDICT.json, event logs, or lock files directly.
- Never manufacture the legacy TTY confirmation token.
- Never add push, merge, deploy, publish, send, payment, or unrelated remote authority.
- Do not ask the operator to tune model, effort, retry, cost, token, wall-clock,
concurrency, or provider flags when current trusted Loop configuration and
packet defaults can decide them safely.
- A human request to **implement, build, fix, finish, execute, run, continue, or
otherwise carry out** the mission is execution intent. Creating the packet is
part of that one request; do not stop merely to hand the operator an enqueue
command.
- A human request explicitly limited to **draft/spec/plan/inspect only** is
draft-only intent. Never enqueue draft-only work.
- These intent rules apply whether this skill was invoked explicitly or the
operator used a plain-language prompt asking Claude to create a Loop packet.
## New specification (normal flow)
1. Confirm the working directory is the target Git repository.
2. Resolve repository identity BEFORE creating the run:
* inspect configured Git remotes;
* decide the packet classification from actual current state, not intended future state;
* `local_only` means no configured remote;
* when a private GitHub review surface is part of the