---
name: proposal-from-discovery
description: "Translate a discovery conversation into a scoped, internally consistent proposal draft. Use when the user requests proposal from discovery. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Proposal from Discovery

Translate a discovery conversation into a scoped, internally consistent proposal draft.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Discovery notes or transcript
- Approved pricing
- Delivery constraints
- Required proposal format

## Methods

### Resolve the brief

Extract the actual problem, desired outcome, current systems, constraints and success criteria. Mark unresolved details instead of filling them with sales assumptions.

### Define deliverables

Connect each deliverable to the agreed problem and separate included work, optional work and exclusions. Distinguish configuration from custom development.

### Reconcile commercial terms

Reconcile fees, units, milestones, dates and dependencies across the entire proposal. Never reuse another client’s rates, contact details or commercial terms.

### Render and review

Render the final artifact and inspect every page for truncation and conflicting copy. Return the draft and unresolved decisions; signing and sending are separate actions.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.