What problem does it solve? Projects often start without an explicit, agreed boundary, so scope creep, stakeholder disagreement, and uncontrolled change follow. This Skill turns an initial intent into a documented scope baseline — what is in, what is out and why, and under which constraints — so every downstream engineering decision is made against a shared, testable definition. ## Core Features & Use Cases - Boundary Definition: Records in-scope users, systems, capabilities, and deliverables, plus an explicit out-of-scope list where every exclusion carries a rationale. - Constraint & Assumption Register: Captures regulatory, budget, timeline, and platform constraints with owners and validation paths. - Change Control: Assesses proposed changes for boundary impact and routes scheduling consequences to prioritisation. - Use Case: At the start of a Specify phase, a Product Owner and AI Program Manager use this Skill to produce a Project Definition that requirements analysis, solution architecture, and acceptance criteria all derive from. ## Quick Start Use the Forge-Scope-Definition skill to draft a project scope definition for this initiative, including in-scope items, explicit exclusions with rationale, and a constraint and assumption register.
