Use when material arrives without a fully formed ask or the ask is thinner than the data suggests. Proposes the intent as a confirmation-ready proposal with a next-step sketch. Not for an interview — use interview-me.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add OutlineDriven/odin-claude-plugin --skill intent-proposal --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Intent Proposal?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/outlinedriven-intent-proposal)More formats (shields.io, HTML) on the badges page.
---
name: intent-proposal
description: 'Use when material arrives without a fully formed ask or the ask is thinner than the data suggests. Proposes the intent as a confirmation-ready proposal with a next-step sketch. Not for an interview — use interview-me.'
---
# Intent proposal
## Contract
| Field | Bound contract |
|---|---|
| Trigger | Material arrives without a fully-formed ask, or the ask reads thinner than the data suggests |
| Authority | Read-only; no file, VCS, credential, paid, published, deployed, or remote mutation |
| Side effect | None; emits a one-line intent proposal plus next-step sketch for confirmation |
| Done | User's reply is short: yes, correction, or adjust; if they had to compose the ask from scratch, the skill failed |
## Inputs
- The handed-over material (files, repository, paste, chat scrollback, or any data drop). Required.
## Procedure
1. Read every piece of the handed-over material end to end before proposing anything.
2. State the intent read from the data, in one line grounded in what the data actually shows.
3. Sketch briefly the next action on that intent.
4. Propose only to confirm: right, wrong, or adjust.
5. If two intents are plausible, propose the likelier and name the other in a clause. One intent per turn.
## Failure and recovery
- Data too thin to propose from: say so and stop. Do not fall back to asking.
- Proposal without reading: this is a guess; re-read the data before proposing.
- User composes the ask from scratch: the proposal was wrong or a question in disguise; redo the proposal grounded in the data.
- No mutation occurs on any path; rollback is trivial: nothing was changed.
## Output
A one-line intent proposal grounded in the data, a next-step sketch, and a confirm/correct/adjust prompt. No file, state, or remote change.
Is this your skill, or is something wrong with this listing? . Author removals are honored within 72 hours.
No comments yet. Be the first to comment!