Trace a change before you make it.

Before changing a function, find its callers with Tower and look up compatibility decisions in ZPM. Put the regression checks in an AWF CLI workflow so a teammate can run them too.

Find the callers before changing a function

With Tower and its language-server extension configured for your language, jump to a definition and find its references. Inspect a caller and its tests before asking an agent to change the function.

Explore code navigation with Tower

If the team has recorded why an older caller still needs the current behavior, an agent can retrieve that decision from ZPM in its next session. Use it to decide which regression test belongs in the change.

Explore project memory with ZPM

Start with one command

Pick a command your team already runs. Add it as a step in a YAML workflow, name its inputs and define the success transition. The definition makes the execution order visible in a pull request.

Try the local example

Share the repeatable parts

Workflow packs bundle definitions, scripts and prompts. Review a pack in source control, install it and invoke its workflow by name. The hello pack provides a small example you can inspect end to end.

awf workflow install awf-project/awf-workflow-hello
awf run hello/hello --input name=World --output=buffered
Inspect the hello workflow pack