[01] LOOP
DesignintervalHardenedTemplate

Reframe Ops on Autopilot

Inspired by Reframe — AI-native, hardware procurement marketplace. Loop until the workflow is current, exceptions are owned, and human sign-off is captured where required.

Inspired by Reframe

by Trooper

Kickoff prompt
/loop 30m Start the "Reframe Ops on Autopilot" loop.

Inspired by Reframe (http://usereframe.ai).

Goal: open work triaged, exceptions owned, and core design workflow current with audit trail
Max iterations: 20
Between iterations run: Report open queue items, stale tasks, failed automations, and items awaiting human approval for Reframe
Exit when: zero open items without owner or explicit escalation, all external actions approved or sent, and systems of record current

Step 1 — Intake demand: Collect specs, quantities, lead times, and vendor constraints.
Step 2 — Source and compare: Rank suppliers or components by spec, cost, and availability.
Step 3 — Draft orders: Prepare POs or build configs with cited BOM lines.
Step 4 — Human approval: Require sign-off before spend or manufacturing commits.
Step 5 — Track fulfillment: Monitor delivery, QA, and exception handling to close.

## Before you start

Connect plugins:
- GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs.
- Figma (required) — Inspect designs, dimensions, assets, and handoff notes.
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped.
- CI debugging (optional) — Read failing checks, logs, and the smallest actionable root cause.
- Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial.
- Visual design QA (optional) — Compare implementation against visual expectations and capture regressions.
- Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.

Steps

1. Intake demand

Collect specs, quantities, lead times, and vendor constraints.

2. Source and compare

Rank suppliers or components by spec, cost, and availability.

3. Draft orders

Prepare POs or build configs with cited BOM lines.

4. Human approval

Require sign-off before spend or manufacturing commits.

5. Track fulfillment

Monitor delivery, QA, and exception handling to close.

Flow diagram

Guardrails

Rules the agent must follow so it cannot cheat the exit condition.

  • Require human approval before customer-facing sends, payments, or legal submissions unless pre-approved templates apply
  • Preserve full audit trail linking source data to every automated action
  • Escalate compliance, safety, or regulatory-sensitive items immediately

More Design loops