A new Deliverable in the packaging Phase, produced by a delivery planner
after validation.
- The planner writes the plan as data: work packages that name the Elements
they deliver, and activities with days, what each follows, and whether the
team or the customer owns it.
- Code checks the plan against the design: every Element belongs to a work
package, and the activities can be scheduled.
- Code computes the schedule, with no more of the team's activities at once
than the team has people, and the critical path.
- Code writes the WBS dictionary (a work package is done when the Checks on
its Elements pass), the activity sequence and a timeline on a relative axis
from Day 0.
- The plan is checked against the delivery window from the agreed scope; over
it, the Deliverable says by how much and names the critical path.
- With a start date it also gives calendar dates and a Mermaid Gantt chart.
- The timeline is added to the solution guide, and the plan's length is in
execution.json and the packaging Approval.
Not run with real models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A scope spec is a YAML file of what the customer wants and the facts a design
depends on, complete or partly filled. It sits beside the Intent, which stays
in the customer's words.
- skills/scoping holds a provider-neutral catalogue of 63 fields; the Cloud
provider's bundle supplies the values it allows for the fields left to it.
- app/scope.py reads a spec against the catalogue with no model: it refuses an
unknown field or a value of the wrong type, and yields what is stated, what
is left to the agent, what is unknown and how pressing each gap is. A field
may say ask, decide or not_applicable.
- ExecutionEngine.start(scope=...), /generate, A2A metadata and evaluation
cases accept one. Its statement is the request, its engagement reference
names the Customer case, and its run options apply. A pre-approved start is
refused when an essential field is not settled.
- The spec as supplied is kept unaltered beside a completed copy with
assumptions, gaps, provenance, readiness and a status.
- Every Specialist is shown the spec and given the Skill: a stated choice
binds, exclusions are out of scope.
- Covers workloads and platform foundations; case-08-landing-zone starts from
a benchmark spec.
Plans for scoping (iteration 9) and the work breakdown structure (iteration
10, nothing built), and the design spec they come from. Not run with real
models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>