build-scope-of-work

Generate a phase-structured Scope of Work HTML from an approved Project Brief.

Updated Apr 26, 2026

Search Tags:#automation #project-management #document-generation #scope-of-work #build-sow

Ready to run

npx skills add https://github.com/aoecosystem/project-foundations --skill build-scope-of-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-scope-of-work
Source: https://github.com/aoecosystem/project-foundations/tree/main/.cursor/skills/build-scope-of-work
Command: npx skills add https://github.com/aoecosystem/project-foundations --skill build-scope-of-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a filled Scope of Work HTML from a previously approved Project Brief, accelerating the handoff to execution and ensuring consistency with the approved brief.

Core Features & Use Cases

Reads the approved BRIEF and scope-of-work-template.html, validates Stage BRIEF_APPROVED, and assembles a complete SoW document structured into Phases 1-10.
Applies Architecture Style rules (monolith, hybrid, microservices, serverless) from the brief and corresponding system-architecture guidelines to tailor the SoW content.
Writes scope-of-work/<slug>-scope-of-work.html and advances Stage to SOW_DRAFT, ready for review.

Quick Start

Kick off the SoW generation by issuing /build-scope-of-work after the brief is BRIEF_APPROVED.

Frequently Asked Questions about build-scope-of-work

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

FAQPage Schema

How do I generate a scope of work document from an approved project brief?▼

To generate a scope of work, this tool reads your approved project brief HTML and a scope-of-work template, then assembles a structured SoW document. It automatically writes the output as an HTML file and transitions your project stage to SOW_DRAFT for review.

What is needed to automate scope of work generation for my project?▼

Automating scope of work generation requires an approved project brief in HTML format and a scope-of-work template. The system verifies the project stage is BRIEF_APPROVED by reading session state before creating the structured HTML output.

Can I tailor the scope of work content for different architecture styles like microservices or serverless?▼

Yes, the scope of work generation applies architecture style rules from the approved brief, including monolith, hybrid, microservices, and serverless. It uses these styles to tailor the SoW content according to corresponding system-architecture guidelines across phases.

What's the best way to structure a project scope of work into phases automatically?▼

The best way to structure a scope of work into phases is by using a template-driven generation tool. It reads the approved brief and automatically assembles a complete SoW document structured into phases one through ten.

Why does scope of work generation fail if the project brief is not approved?▼

Scope of work generation fails without an approved brief because the tool checks the session state to verify the BRIEF_APPROVED stage. This validation ensures the generated SoW maintains consistency with the finalized project requirements before writing the HTML output.