sow-writelisted

Write professional Statements of Work (SOW) in full (15-section enterprise) or summary (9-section contract extraction) mode. Auto-detects language from input documents, supports English and Italian with language packs. Produces structured markdown with optional research subagents for domain gaps. Use this skill whenever the user wants to write a SOW, create a statement of work, draft a proposal, write a capitolato tecnico, prepare an offerta, or mentions 'scrivi SoW'. Also triggers for 'project proposal', 'scope document', 'service agreement draft', or any request to formalize project scope into a deliverable document.
MrBogomips/claude-code · ★ 0 · Data & Documents · score 72

Install: claude install-skill MrBogomips/claude-code

# SOW Write — Statement of Work Generator ## 1. Overview This skill writes professional Statements of Work from project briefs, PRDs, contracts, meeting notes, or any combination of input documents. It operates in two modes: - **Full mode** (15 sections) — enterprise SOW for new engagements, detailed technical proposals, or formal bids - **Summary mode** (9 sections) — contract-extraction SOW for existing agreements, renewals, or scope addenda The skill auto-detects language from input documents and produces output in the detected language. When language is ambiguous (mixed-language inputs), it asks the user to choose. Language packs provide localized section headers, boilerplate text, and legal terminology. **Output directory:** `docs/outbox/` (configurable) **Connector support:** Skills degrade gracefully without connectors. See `CONNECTORS.md` for the full registry. - If **~~knowledge base** is connected: pull existing project templates and corporate standards - If **~~document storage** is connected: search for related documents and past SOWs - If **~~CRM** is connected: pull client context for personalization - If **~~calendar** is connected: check team availability for scheduling sections - If **~~email** is connected: share SOW drafts with stakeholders --- ## 2. Pipeline ### Step 1 — Input Analysis Read all provided documents (notes, PRDs, briefs, contracts, emails, meeting transcripts). For each document: - Identify document type (brief, contract, RFP, meet