joeaksel

Sow Create — Development skill for Claude Code

Development community

This Claude Code skill should be used anytime the user asks to generate a scope of work or SOW.

How to install Sow Create

This entry records only its repository, not the path inside it, so there is no exact command to give. Open joeaksel/sow-create and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Sow Create does

This Claude Code skill should be used anytime the user asks to generate a scope of work or SOW.

Alternatives in Development

Claude API — Build apps with the Claude API or Anthropic SDK 94.1k ★
Claude Integration Guide — FOR CLAUDE CODE: When a user asks you to integrate components from this showcase repository into their project 9.3k ★
Connector Discovery Skill — Triggers: - Invoked during onboarding Phase 3.5 (after archetype detection) - Invoked by capability-suggester 209 ★

README

SOW Generator — Claude Code Skill

A Claude Code skill that turns a short project description into a complete Scope of Work (SOW) and Level of Effort (LOE) summary for professional services engagements.

Overview

Writing a SOW by hand is slow, inconsistent, and easy to get wrong — hours missed, resource types mis-assigned, formatting that doesn't line up with the downstream quoting system. This skill produces two deliverables from a single prompt:

A Word (.docx) document containing Project Summary, Assumptions, Exclusions, Customer Responsibilities, and a fully numbered task list with time estimates
An Excel (.xlsx) LOE summary that groups hours by resource type (Project Engineer 1, Project Engineer 2, Network Engineer), with subtotals and a grand total

The contents of the SOW Word docx file is copy/pasted into a quote using CPQ.

Key features

**Structured output built around the real workflow.** The Assumptions, Exclusions, and Customer Responsibilities sections use plain line breaks — no bullets, no numbering — so content pastes cleanly into the downstream quoting system without reformatting.

**Resource-type-aware LOE breakdown.** Hours are split by the kind of engineer who actually does the work: remote and configuration work to a Server Level engineer, on-site deployment to a Desktop Level engineer, infrastructure work to a Network Engineer. Project management is intentionally excluded because PM hours are tracked separately.

**Clarifying questions before generation.** The skill asks for missing context up front and flags known compatibility issues or product limitations *before* producing the SOW — rather than guessing and producing a document that gets thrown out.

**Microsoft Learn MCP integration.** When the project touches Microsoft products (Intune, Azure, Windows, M365, etc.), steps are validated against official Microsoft documentation, avoiding outdated or invented procedures.

**Consistent, contract-ready formatting.** Arial 1