bounds-mode

Files (5)

• LICENSE.txt
• NOTICE.md
• SKILL.md
• openai.yaml · agents/
• hosts.md · references/

SKILL.md (first lines)

# Bounds mode

Use this entrypoint only when explicitly requested. Optimize for accepted work per minute of human attention: preserve the task, resolve routine details from evidence, and keep small requests small. This skill adds no permissions or external actions.

## Route the task

Read the relevant project instructions and available skill descriptions. Load a supporting skill's body only when its phase is needed, through host discovery. Load references conditionally.

| Need | Skill |
| --- | --- |
| Material scope, behavior, or dependency decisions | `bounds-plan` |
| An observed failure or regression | `bounds-debug` |
| A requested review or consequential implementation to check | `bounds-review` |
| An authorized change to finish through PR readiness | `bounds-ship` |
| A stale or inherited PR to reassess and update | `bounds-modernize` |
| Authorized GitHub comments on the user’s behalf | `bounds-leaving-pr-comments` |
| Prior decisions or unfinished work to recover | `bounds-recall` |
| Repeated corrections or avoidable work to examine | `bounds-retro` |
| Agent documentation to create or repair | `bounds-agent-docs` |
| A reusable project verification recipe to establish | `bounds-create-verification` |
| An existing recipe or feature map to refresh | `bounds-maintain-verification` |
| Progress since the user's last message | `bounds-ketchup` |
| Rationale behind existing code | `bounds-why` |
| Downstream effects of a change | `bounds-blast-radius` |
| A code walkthrough or explanation | `bounds-how` |
| Interfaces and state ownership to design | `bounds-architect` |
| Requested prose to tighten | `bounds-unslop` |
| A reusable working-style skill | `bounds-automate-me` |

Keep phases proportional: inspect a typo directly; reproduce a bug first. A request for a plan or review ends with that deliverable; it does not authorize implementation. Preserve relevant specialist skills and native tools.

Carry authorized implementation through the agreed acceptance checks. Use the project's existing verification recipe when useful; creating one is a separate need, not a compulsory phase. Report the outcome, evidence, and consequential gaps. Use independent review when warranted, available, and permitted by existing user and host instructions, under `bounds-review`'s bounded protocol. Reuse authorization already granted.

If a selected skill is absent, say which one. Continue with the available tools when feasible, without pretending it loaded or installing dependencies unasked.

## Continuity

Honor opt-out immediately. Follow the user's continuing task while context retains it; there is no portable sticky-mode switch. Do not persist a mode setting or modify standing instructions. For invocation, fresh-session discovery, or host limitations, read [host behavior](references/hosts.md).

From boundsj/bounds-skills, MIT.

More from boundsj/bounds-skills