approve-scope-of-work

Validate the SOW quality gate and transition the pipeline from SOW_DRAFT to SOW_APPROVED.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/aoecosystem/project-foundations --skill approve-scope-of-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: approve-scope-of-work
Source: https://github.com/aoecosystem/project-foundations/tree/main/.cursor/skills/approve-scope-of-work
Command: npx skills add https://github.com/aoecosystem/project-foundations --skill approve-scope-of-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lock the Scope of Work and transition the pipeline from SOW_DRAFT to SOW_APPROVED, ensuring the SoW quality gate is applied and auditable.

Core Features & Use Cases

  • Enforces the Stage gate and updates session-state when SoW is approved.
  • Verifies critical quality gates including page inventory coverage, placeholders, and universal services integrity.
  • Produces an audit log and presents next valid commands for the workflow.

Quick Start

Run the /approve-scope-of-work trigger to lock the SoW and advance the pipeline to SOW_APPROVED.

Frequently Asked Questions about approve-scope-of-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lock the Scope of Work and advance the pipeline from SOW_DRAFT to SOW_APPROVED?▼

To lock the Scope of Work and advance the pipeline to SOW_APPROVED, trigger the approval process to validate the quality gate, update session state, and append the audit log.

What does the SoW quality gate validate before approving the scope of work?▼

The SoW quality gate validates phases, placeholders, page inventory coverage, universal services integrity, and slug-name match before the scope of work approval transitions the pipeline state.

How do I audit the SoW approval phase in an automated pipeline?▼

Automated SoW approval audits the workflow by validating the quality gate, updating session state, and appending an audit log entry before surfacing the next valid workflow commands.

Can I approve the scope of work if the page inventory has missing placeholders or slug-name mismatches?▼

No, scope of work approval requires passing the quality gate, which enforces page inventory coverage, validates placeholders, verifies universal services, and checks for slug-name match.

What happens to session state after the Scope of Work is approved?▼

After the Scope of Work is approved, the session state updates to reflect the transition from SOW_DRAFT to SOW_APPROVED, enabling the next steps and surfacing valid workflow commands.

Do I need any dependencies installed to run the scope of work approval quality gate?▼

No dependencies are required to run the scope of work approval quality gate, as it operates independently to validate phases, page inventory, and session state before appending audit logs.