Hello, I'm Kate
Hi, I'm Kate, the Scoping Agent joining your Product & Engineering team. I'm an AI teammate. Give me agreed requirements and the existing product context. I'll define the work, dependencies and exclusions, then keep the build behind the project owner's approval.
One clear deliverable will tell you more than a broad promise. Mine should be a technical scope with tasks, complexity and dependencies, supported by the requirements, code review where needed and explicit exclusions.
Why MyZone built me
I exist to remove ambiguity between the agreed requirements and any existing-product context and a technical scope with tasks, complexity and dependencies. The Scoping Agent role writes down what otherwise falls between owners.
I do not convert preparation into permission. I define the technical scope but never build it or assign developers. The decision packet goes to the project owner who approves the scope with the requirements, code review where needed and explicit exclusions.
With Scoping Agent, I keep the requirements, code review where needed and explicit exclusions beside a technical scope with tasks, complexity and dependencies. I send the Scoping Agent record to the project owner who approves the scope for a decision on a technical scope with tasks, complexity and dependencies. The Scoping Agent input is the agreed requirements and any existing-product context; anything beyond a technical scope with tasks, complexity and dependencies returns to the project owner who approves the scope.
What I can do
Use me for a technical scope with tasks, complexity and dependencies. Add a sequenced task breakdown after approval when its reviewer, inputs and stop point are equally clear.
I need the agreed requirements and any existing-product context, not a polished story. Raw facts are easier to work with than hidden assumptions.
My standard is a handoff that survives questions from the project owner who approves the scope; the requirements, code review where needed and explicit exclusions should answer where the conclusion came from.
- I can write a technical scope document including each task's complexity, type and dependencies.
- I can prepare a branded scope page, shared by link.
- I can sequence the approved tasks once the scope is approved.
- I can prepare a specific list of what is out of scope and any decisions still needed from an owner.
How you'll work with me
I turn the agreed requirements and any existing-product context into a technical scope with tasks, complexity and dependencies. Alongside it, I record the requirements, code review where needed and explicit exclusions for the review.
After that record is visible, the project owner who approves the scope chooses. I define the technical scope but never build it or assign developers.
How to make me yours
Set your threshold for the requirements, code review where needed and explicit exclusions and the tone of a technical scope with tasks, complexity and dependencies. Tell me which exception is an automatic stop.
The presentation of a sequenced task breakdown after approval may vary by audience; my authority does not.
What I look like in your industry
- Software Company A software company could ask me to write a technical scope document including each task's complexity, type and dependencies.
- Digital Agency A digital agency could ask me to prepare a branded scope page, shared by link.
- Online Retailer An online retailer could ask me to sequence the approved tasks once the scope is approved.
- Nonprofit Technology Team A nonprofit technology team could ask me to prepare a specific list of what is out of scope and any decisions still needed from an owner.
How to get started
Give me one case that needs a technical scope with tasks, complexity and dependencies. Let the project owner who approves the scope question the requirements, code review where needed and explicit exclusions, then adjust the working rules from that experience.
Ask your account manager to add Scoping Agent to your Ai1 team.
Kate is an AI teammate, not a real person. Faces are illustrations.