How it works Capabilities Methods Workflows Why MCP FAQ Book a demo
Built-in prompt

Review-ready scope

Turn a rough draft into a scope your reviewer can approve, with every change tracked.

4steps 1human checkpoint 9Apropo methods
← All workflows

For: Delivery leads and reviewers

Before a quote goes out, someone has to tidy names, add descriptions, split scenarios and make sure nothing was overwritten along the way.

You sayMake project <uuid> review-ready: clear names, descriptions on each module, and an MVP version next to the full scope.

Run the MCP prompt workflow_review_ready_scope, or just describe the goal: an agent can load the same steps with apropo_get_workflow.

  1. Read before writing

    The agent reads the versions, the tree and the description rules.

    apropo_list_project_structuresapropo_get_project_structure_detailsapropo_get_project_node_description_settings
  2. Human decision

    Approve the plan

    The agent lists what it intends to change. Nothing is written until you approve.

  3. Apply safe edits

    It renames nodes, writes descriptions and creates a scenario version, refreshing the lock_version after every edit.

    apropo_update_project_nodeapropo_set_project_node_descriptionapropo_set_project_structure_descriptionapropo_add_project_structureapropo_rename_project_structure_version

  4. Share for review

    It returns a share link to the exact version.

    apropo_get_project_sharelink

What you get

A clean, described scope, an MVP scenario and a link a reviewer can open straight away.

Built-in safeguards

  • Approval is required before any change is made.
  • Concurrent edits are caught by the lock_version check, so nobody's work is overwritten.

Want to see this run on
your own brief?

Book a demo and we will run this workflow live with your tools, with a person approving every step that matters.

Book a demo All workflows