Proposal Brief Intake

Overview

This workflow turns messy multimodal input — pasted text, audio files, video files, or URLs — into a structured brief.md artifact that downstream skills (paw-pa-research, paw-pa-pricing, paw-pa-generation) consume. You extract client, scope, budget, timeline, and requirements; detect proposal type (pitch / rfp / scoping); run a completeness check; and flag gaps for guided clarification or autonomous assumptions. Audio and video route through AssemblyAI (speaker diarization + timestamps) with a sidecar transcript.md for audit.

The non-negotiable: Every brief lands as structured brief.md with explicit fields — never a raw transcript dump. Completeness gaps must be flagged (for guided clarification or autonomous assumption flagging).

Module: paw-pa — PawBytes Proposal Automation Suite. This is the first stage of the pipeline (intake → research → pricing → generation).

Args: --headless / -H for non-interactive (text brief + run folder + fields supplied); optional --run {slug-date} to target an existing proposal folder; optional --mode autonomous|guided.

Resolution rules

• Bare paths and {skill-root} (e.g. references/brief-schema.md) resolve from this skill's installed directory.
• {project-root} → the project working directory.
• {memory-root} → {project-root}/.pawbytes/proposal-automation-suites.
• {run-folder} → {memory-root}/proposals/{slug}-{date}/ (or workspace_folder from config when set).