Define the missing capability
Describe the page, user, behavior, data boundary, and success measure without needing selectors or code.
Describe what you want to add or change in one box. Get a ready-to-use build prompt for a Moxby Mod.
Write the idea as loosely as you would explain it to a teammate. The planner fills in scope, interface states, data boundaries, acceptance criteria, edge cases, and tests, then labels anything it had to assume.
Add a Send to Mission action to opportunity pages in a CRM.
01Trigger: opportunity detail pages only
02Read: opportunity title, stage, value, owner, and current URL
03Write: nothing until the user confirms the review panel
04Acceptance: every captured field is visible before submission
05Extension path: save the finished product as a reusable CRM Mission Launcher Mod
Describe the page, user, behavior, data boundary, and success measure without needing selectors or code.
Receive interface states, trigger rules, edge cases, acceptance criteria, permissions, and a test plan.
Use Describe or Watch Me in the real Mod flow, inspect the live site, and keep the finished capability in your browser.
These tools give value before installation and connect the finished plan to the Moxby browser capability built to run it.
No. It creates a plan. Build and run the Mod inside Moxby.
Yes, when you are authorized to use the site and the change respects its rules, privacy, and access controls.
No. The URL is descriptive context only. Use the real Moxby Mod flow when live inspection matters.
No. Describe the visible element and desired behavior. Any proposed target remains provisional until tested.
Chat on any page, build Mods, run Missions, and add ready-made products from the Marketplace.