Scope

Get a comprehensive scope assessment for a work card.

Scope gives you a pre-flight readiness check for any outcome or work card. Before committing to work, run a scope analysis to understand what's required, what's missing, and how ready the item is for execution. Think of it as a structured risk assessment that catches gaps before they become blockers.

How Scope works

The agent analyzes the entity's goal, context, and related information to produce a comprehensive assessment covering six dimensions:

  • Requirements — What needs to be true for this work to succeed
  • Constraints — Limitations and boundaries on how the work should be done
  • Dependencies — Other items, people, or resources this work depends on
  • Acceptance criteria — Specific conditions that must be met for the work to be considered done
  • Gaps — Missing information, unclear requirements, or unresolved questions
  • Readiness assessment — An overall evaluation of whether the item is ready to start

Running Scope

  1. Open the outcome or work card

    Navigate to the entity you want to assess.

  2. Click AI → Analyze readiness

    Click the AI button and select Analyze readiness from the dropdown.

  3. Review the assessment

    The AI drawer opens with a structured report covering all six dimensions, plus a reasoning trace showing how the agent arrived at its conclusions.

The Scope results panel showing sections for Requirements, Constraints, Dependencies, Acceptance Criteria, Gaps, and a Readiness Assessment summary

Understanding the results

Requirements

A list of things that need to be in place. For example: "API endpoint for user data must be available" or "Design mockups need to be approved."

Constraints

Boundaries on the work: "Must not modify existing database schema" or "Budget limited to 40 hours."

Dependencies

Other cards, outcomes, teams, or external resources this work depends on. The agent identifies both internal dependencies (other cards in the same outcome) and external ones (third-party APIs, stakeholder approvals).

Acceptance criteria

Specific, testable conditions for completion. These are more granular than success signals — they describe exact checks that should pass.

Gaps

This is often the most valuable section. Gaps highlight what's missing:

  • Undefined requirements
  • Unresolved design questions
  • Missing stakeholder input
  • Ambiguous scope boundaries

Readiness assessment

A summary evaluation of the item's readiness to start, considering all the dimensions above.

Run Scope before activating a sprint. Assessing each committed card helps you catch missing dependencies and unclear requirements while there's still time to address them.

Scope analysis results are saved as entity documents attached to the outcome or card. You can review them later from the Resources row without re-running the agent.

Next Steps