workflow-scope

Create a plan document with a scope statement covering the problem, users, and success criteria, then list explicit in-scope items and out-of-scope exclusions with reasons. This Skill generates that document from a template and requires stakeholder approval before work continues.

Phase 5 defines the how: strategy, alternatives, and decisions. Phase 6 defines the what: the formal scope statement with explicit in-scope and out-of-scope lists. The strategy informs the scope, but the scope is a separate artifact requiring its own approval.

Document an explicit out-of-scope list with reasons for each exclusion, and require that every task trace back to an in-scope item. If a task lacks traceability or exceeds 25 percent of total effort, pause and decide whether to expand scope formally or create a new work package.

A traceability table mapping RC items to tasks is required only when the plan derives from formal analysis with documented RC entries. Every high or medium priority RC must map to at least one task. Mechanical work without formal RCs can omit the table.

No. The phase completes only when the plan file exists with the scope-approved checkbox marked, ROADMAP.md links the work package, and the user explicitly confirms the scope in the current session. The Skill stops at a human gate and waits.