Produces the architecture-related fields of sowdata (architecturedescription, technologystack, architecturecomponents, architectureintegrations, customerprimarydomain — domain only when set by a sibling skill, never by this one) and renders the architecture PNG via generatearchitecturediagram. Invoked by the root SOW orchestrator agent during Phase 2 Step D, AFTER requirements (Step A), delivery plan (Step B) and scope boundaries (Step C) snapshots are already in sowdata. NOT responsible for Partner Overview, Customer Overview, or Executive Summary — those belong to sow-narrative. NOT responsible for the user review presentation — the root orchestrator owns that.
EnglishConducts a short guided interview when the user wants to start a SOW without uploading project documents. Persists the structured summary to state['app:sow:intakesummary'] via the savesowintakesummary tool, then hands control back to the root for savesowmetadata and the section flow. Trigger phrases include "quero criar uma SOW", "create a SOW", "responder perguntas guiadas", "start with a guided briefing", "começar pelo briefing", and similar requests where the user has explicitly chosen the guided interview path. Do NOT trigger when the user has already attached project documents — that flow uses loadartifacts directly. Do NOT trigger for SOW content generation, validation, or document assembly — those belong to the section skills and the quality loop.
EnglishProduces the requirements fields of sowdata — functionalrequirements and nonfunctionalrequirements — with cross-validation between the two lists so frvsnfr contradictions and subjectivenfrtarget defects are caught BEFORE the validation critic ever sees them. Invoked by the root SOW orchestrator agent during Phase 2 Step A, BEFORE delivery plan, scope boundaries, architecture, or narrative. Production-grade NFR Reliability rules (anti-uptime / anti-SLA) are enforced in this skill; downstream skills inherit the assumption that Reliability is already correctly phrased.
EnglishProduces the contractual-surface fields of sowdata — assumptions, outofscope, changerequestpolicytext, handoverdisclaimers, and risks — as one tightly-coupled cluster. The five lists are produced together because every assumption needs an OOS counter-anchor, every handover statement needs a matching NFR / Reliability phrasing, and the AI/ML non-determinism disclosure must reconcile across assumptions, OOS, and handover. Invoked by the root SOW orchestrator agent during Phase 2 Step C, AFTER delivery plan (Step B) so deliverables are available as counter-anchors.
EnglishIncludes Sow Architecture, Sow Guided Intake, Sow Requirements, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Sow Architecture
Produces the architecture-related fields of sowdata (architecturedescription, technologystack, architecturecomponents, architectureintegrations, customerprimarydomain — domain only when set by a sibling skill, never by this one) and renders the architecture PNG via generatearchitecturediagram. Invoked by the root SOW orchestrator agent during Phase 2 Step D, AFTER requirements (Step A), delivery plan (Step B) and scope boundaries (Step C) snapshots are already in sowdata. NOT responsible for Partner Overview, Customer Overview, or Executive Summary — those belong to sow-narrative. NOT responsible for the user review presentation — the root orchestrator owns that.
Sow Guided Intake
Conducts a short guided interview when the user wants to start a SOW without uploading project documents. Persists the structured summary to state['app:sow:intakesummary'] via the savesowintakesummary tool, then hands control back to the root for savesowmetadata and the section flow. Trigger phrases include "quero criar uma SOW", "create a SOW", "responder perguntas guiadas", "start with a guided briefing", "começar pelo briefing", and similar requests where the user has explicitly chosen the guided interview path. Do NOT trigger when the user has already attached project documents — that flow uses loadartifacts directly. Do NOT trigger for SOW content generation, validation, or document assembly — those belong to the section skills and the quality loop.
Sow Requirements
Produces the requirements fields of sowdata — functionalrequirements and nonfunctionalrequirements — with cross-validation between the two lists so frvsnfr contradictions and subjectivenfrtarget defects are caught BEFORE the validation critic ever sees them. Invoked by the root SOW orchestrator agent during Phase 2 Step A, BEFORE delivery plan, scope boundaries, architecture, or narrative. Production-grade NFR Reliability rules (anti-uptime / anti-SLA) are enforced in this skill; downstream skills inherit the assumption that Reliability is already correctly phrased.
Sow Scope Boundaries
Produces the contractual-surface fields of sowdata — assumptions, outofscope, changerequestpolicytext, handoverdisclaimers, and risks — as one tightly-coupled cluster. The five lists are produced together because every assumption needs an OOS counter-anchor, every handover statement needs a matching NFR / Reliability phrasing, and the AI/ML non-determinism disclosure must reconcile across assumptions, OOS, and handover. Invoked by the root SOW orchestrator agent during Phase 2 Step C, AFTER delivery plan (Step B) so deliverables are available as counter-anchors.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Sow Architecture skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.