CUSTOM WORKFLOWS

Give your workflow
a Run button

GenieWorks turns your team’s method into a shared tool. Choose a recipe, supply its business inputs, and let the workflow carry the investigation, decisions, and result.

Follow the work

01 · SUPPLY THE BUSINESS CONTEXT

Maya fills in the form
The recipe carries the method

Maya selects Create Project Proposal and supplies the goal, audience, constraints, and decision owners. The recipe defines what to investigate and what the proposal must contain.

She can run the saved process without installing a CLI or reconstructing the author’s command and prompt.

02 · INVESTIGATE AND RESOLVE THE CHOICE

Reuse the foundations
Agree on the first useful scope

GenieWorks finds that existing account provisioning can support the goal. Public signup would also introduce billing and abuse-control work.

That changes the proposal. It brings the pilot-versus-public decision to the team, then carries the agreed constraints into the result.

APP-73 · Proposal history

  1. Maya Product lead

    Ran Create Project Proposal with the onboarding goal and enterprise audience.

  2. GenieWorks AI engineer

    We can reuse provisioning. Public signup adds billing and abuse controls. Start with an invited enterprise pilot?

  3. Maya Product lead

    Yes, pilot first. @Alex, can we keep our current account approval?

  4. Alex Engineering lead

    Yes. Reuse provisioning and manual approval. Add guided setup after the invitation.

  5. GenieWorks AI engineer

    Proposal ready for review: invited-pilot scope, delivery phases, risks, and success criteria. Pilot customers, targets, and timing remain open.

03 · REVIEW THE DELIVERABLE

A proposal the team can make decisions from

The form and output describe the same work. The result preserves the invited-pilot decision and the existing approval flow, with remaining choices still visible.

The proposal is ready for team review. It does not approve implementation, set a launch date, or remove the existing account-approval step.

04 · REUSE THE TEAM’S PROCESS

The author defines the method
The team can run it

A versioned recipe keeps the input form, investigation, and expected output together. The next teammate can use the same method and inspect the run’s inputs, decisions, and result.

Workflow author

Define the investigation

Choose the inputs, project context, tools, decision points, and deliverable.

Teammate

Run the saved recipe

Supply business inputs and answer consequential questions in the shared workflow.

Team record

Inspect how it got there

Keep the recipe version, inputs, decisions, and result with the run.

CONTINUE THE WORK

Turn the agreed proposal into work

Use the accepted scope as the starting point for detailed specifications.

Discuss your workflow
Explore specification

Silent visual walkthrough · Narration shown above