proposal

---
name: proposal
description: Formal business case and proposal generator that produces customer-facing HTML documents with ROI framing and implementation details. Use when user says "create a proposal", "business case", "proposal for [company]", "formal pitch", or asks for a closing document.
---

# /octave:proposal - Octave-Powered Proposal Builder

## Run the task

Read [the task method](references/task-method.md) before selecting context, claims, or output. It is the execution method for this skill. Supporting templates supply structure and styling; populate them from the task method and current evidence, not their illustrative figures or assertions.

Resolve seller draft, completed buyer proposal, or collaborative POC/success plan. Collect and incorporate missing seller inputs across turns. Future measurements may stay open in a defined worksheet. Quantify supported value with auditable units, costs and assumptions; compare the actual alternative including DIY/inaction.

Use [GTM context](../shared/gtm-context.md) for strategic tasks and [evidence and inputs](../shared/evidence-and-inputs.md) for material claims and missing facts. A narrow list/get or a render-only handoff does not require unrelated research. Read [host runtime](../shared/host-runtime.md) for available tools, portable resource paths, routing, and review fallback.

Resolve current tool schemas before execution; use returned IDs and pagination. Inventory rows locate records; hydrate selected entities/resources before relying on their contents. Reuse supplied or inherited context and authorization. Ask grouped questions only for material unresolved inputs, continue independent work, incorporate replies, and recheck affected output.

## Usage

```
/octave:proposal <target> [--style <preset>]
```

## References by task

- [delivery summary](references/delivery-summary.md)
- [document sections](references/document-sections.md)
- [html architecture](references/html-architecture.md)
- [octave tool reference](references/octave-tool-reference.md)
- [proposal outline template](references/proposal-outline-template.md)
- [regression checklist](references/regression-checklist.md)
- [style preset menu](references/style-preset-menu.md)

Read only the reference for the selected mode, then the format/layout references when rendering. Do not repeat intake or change approved claims when routing to a renderer.

## Delivery and changes

Apply [output readiness](../shared/output-readiness.md) to text and artifacts. HTML also uses the [review protocol](../shared/protocol.md) and the matching format checks. A working preview can be shared with its status; unrun checks are NOT RUN. Reviewers return findings on an immutable version; one author applies edits and rechecks the final version.

For visual output, inherit the selected sender/workspace brand through [brand kit usage](../shared/brand-kit-usage.md); honor an explicit override and avoid repeated brand extraction. Public hosting requires the approved audience and publish manifest, followed by URL/access/link verification.

For comparisons, trends or rates, use the [analytics contract](../shared/analytics-contract.md). Only requested persistence loads [workspace mutations](../shared/workspace-mutations.md); report changes as applied only after scoped readback.

• SKILL.md 3 KB
• references/delivery-summary.md 1 KB
• references/document-sections.md 16 KB
• references/html-architecture.md 4 KB
• references/octave-tool-reference.md 4 KB
• references/proposal-outline-template.md 2 KB
• references/regression-checklist.md 4 KB
• references/style-preset-menu.md 1 KB
• references/task-method.md 4 KB