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

Template to tailored project

Start from a proven template and extend it to fit a new client's documents.

4steps 1human checkpoint 12Apropo methods
← All workflows

For: Teams with repeatable project types

Teams keep good templates, but adapting one to a new set of requirements still means copying and re-typing.

You sayCreate a project from our mobile app template and adapt it to these requirements.

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

  1. Pick workspace and template

    The agent lists workspaces and searches templates. If the template does not exist it stops instead of guessing.

    apropo_list_workspacesapropo_list_templatesapropo_get_template_details

  2. Create the project

    It creates the project as a copy of the template.

    apropo_create_project_from_template
  3. Human decision

    Choose how to adapt

    You choose: Strategy B (default) adds new scope next to the template without duplicates. Strategy A replaces the copied structure and needs your explicit confirmation.

    apropo_add_project_batch_treeapropo_add_project_sectionapropo_add_project_moduleapropo_add_project_featureapropo_add_project_taskapropo_delete_project_node

  4. Verify and share

    It reads the final tree, checks that every required node exists and returns the links.

    apropo_get_project_structure_treeapropo_get_project_sharelink

What you get

A project that keeps the template's proven estimates and adds only the scope that is new.

Built-in safeguards

  • Strategy A deletes nodes only after explicit confirmation, one at a time.
  • Every change is read-before-write with the latest lock_version.

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