statement-of-work-author

name	statement-of-work-author
description	Author a Statement of Work (SOW) / Project Charter from a discovery brief, lead form, or kick-off interview. Covers all 12 SOW skeleton fields (objectives, scope in/out, deliverables, assumptions and constraints, engagement model, team and roles, schedule and milestones, pricing and invoicing, acceptance criteria, IP and confidentiality, change control, warranty and support, governance cadence) per modules/cuo/docs/appendices.md (§13 Software Development Process) §4.9. Halts at PLAN approval and HITL gates. Chains naturally into statement-of-work-audit by default. Use when user asks to "draft a statement of work" or "create the statement of work". Do NOT use for "audit existing statement of work" (use statement-of-work-audit instead).
license	Apache-2.0
metadata	{"version":"1.0.0","module":"skill","stage":"a","cyberos-template":"statement-of-work@1","cyberos-rubric-target":"sow_rubric@1.0"}
allowed_memory_scopes	{"read":["project:*","company:locked-decisions","company:values","memories:decisions","memories:projects","client:*"],"write":["project:*","memories:projects"]}
allowed_mcp_tools	["kb.read","kb.search","memory.search","memory.write_memory","audit.append","chat.notify"]
escalation	{"to_persona_on_legal":"cuo-clo","to_persona_on_security":"cuo-cseco","to_persona_on_compliance":"cuo-clo","to_human_on_irreversible":true}
invocation_modes	["standalone","chained"]
expects	{"schema_ref":"./envelopes/input.json","required_fields":["source_files","output_dir","client_name"],"optional_fields":["manifest_path","engagement_model","target_close_date","caller_persona","trace_id","chain_to"],"standalone_interview_ref":"./STANDALONE_INTERVIEW.md"}
produces	{"schema_ref":"./envelopes/output.json","output_kind":"artefact","human_summary_ref":"./HUMAN_SUMMARY.md"}
depends_on_contracts	[{"id":"project-brief","version":"v1","purpose":"input_schema","pin_path":"cyberos/skill/contracts/project-brief/"},{"id":"nats-subjects","version":"v1","purpose":"wire_protocol_emission","pin_path":"cyberos/skill/contracts/nats-subjects/"}]
exposable_as	{"internal":true,"agent_plugin":true,"mcp_tool":true,"partner_connector":false}
audit	{"emit_to":"genie.action_log","row_kind":"artefact_write","payload_hash_field":"sow_hash","explanation_pane":"required"}
confidence_band	{"default":0.7,"defer_below":0.5,"cite_sources":"required"}
untrusted_inputs	{"wrap_in_marker":"untrusted_content","injection_scan":"required","on_marker_hit":"surface_to_human"}
self_audit	{"invariants_ref":"./INVARIANTS.md","check_at":["on_node_boundary",{"on_audit_row_count":25},"on_completion"],"anomaly_signals":{"confidence_low_streak":{"threshold":3,"window":10},"user_correction_streak":{"threshold":2,"window":5},"denylist_near_miss_streak":{"threshold":2,"window":20},"scope_rejection_streak":{"threshold":1,"window":1},"citation_missing_streak":{"threshold":2,"window":10}},"on_breach":{"emit":"refinement_proposal","pause_pipeline":true,"resume_token_field":"refinement_run_id"}}
human_fine_tune	{"fine_tuner_role":"cpo","review_required":{"on_minor_bump":false,"on_major_bump":true,"on_safety_change":true},"signals_to_initiate":[{"acceptance_rate_below":0.6},{"hitl_pause_rate_above":0.4},{"drift_signal_count_above":3},"user_complaint_received","regulator_inquiry_received",{"self_audit_refinement_proposal_count_above":2}],"procedure_ref":null,"required_artifacts":["changelog_entry","acceptance_test_added","memory_refinement_entry"],"blackout_windows":[]}
determinism	{"reproducible":false,"fixity_notes":"SOW authoring includes judgement (pricing, scope, milestones). Manifest state IS reproducible. Re-running on settled state is a no-op except for last_audit_at refresh."}
emitted_source_freshness_tier	30
gated_until_phase	null
untrusted_content_wrapping	required

statement-of-work-author — Statement of Work generator

Authors a Statement of Work (SOW) / Project Charter from a discovery brief, lead form, or kick-off interview. Implements the 12-section skeleton from modules/cuo/docs/appendices.md (§13 Software Development Process) §4.9. Chains naturally into statement-of-work-audit.

prompt_revision: sow_author@1.0.0

When to invoke this skill

CUO routes here when the user wants to:

• "Draft a SOW for ."
• "Turn this discovery brief into a Statement of Work."
• "Update the SOW with the new pricing terms."
• "Generate the project charter for ."

If the user wants to audit an existing SOW instead of authoring, route to statement-of-work-audit.

Self-test preamble

CONTRACT_ECHO
skill_id:                        statement-of-work-author
skill_version:                   1.0.0
prompt_revision:                 sow_author@1.0.0
template_version:                statement-of-work@1   (loaded from cyberos/skill/contracts/project-brief/template.md plus §4.9 skeleton)
output_dir:                      <from caller>
manifest_path:                   <from caller; default: <output_dir>/manifest.json>
naming_pattern:                  SOW-{client-slug}-{YYYYMMDD}.md
batch_size:                      1 (SOWs are authored one at a time)
hitl_categories:                 [pricing_terms, scope_boundary, ip_assignment, data_processing_addendum,
                                  acceptance_criteria, governance_cadence, regulatory_compliance,
                                  customer_quotes]
hitl_policy:                     HALT_ON_PAUSE
max_iterations:                  10
re_entrancy:                     idempotent_on_manifest_state
untrusted_content_handling:      spotlight_xml_tagged
file_scope:                      MUST NOT write outside output_dir
inputs:
  source_files:                  [<list of paths with media_type>]
  client_name:                   <required>
  engagement_model:              <fixed_price | time_and_materials | dedicated_team | staff_augmentation | managed_services>
  source_hash:                   <sha256>
phase:                           <PLAN | WORKER | RESUME>

§1 The 12 SOW sections (per SDP §4.9)

Every authored SOW SHALL contain these sections in this order:

1. ## 1. Objectives and Success Criteria — what we are doing and how we will know it worked.
2. ## 2. Scope — split into ### In Scope and ### Out of Scope. Minimum 3 bullets each.
3. ## 3. Deliverables — concrete artefacts the client receives. Each item has a name, format, owner, and target date.