Back to Founding Engineer
Grok Bot · guided setup

Build Founding Engineer in Grok Bot

Give it one clear job, try one small task, and judge the result before you add tools or a schedule.

Not yet tested in Grok Bot
  1. 1

    Open Grok Bot

    You need access to Grok Bot. In the app, choose New → Create new Bot, then open Edit Profile. Bot Cabinet cannot install this Bot in your account for you.

    Open Grok Bot
  2. 2

    Add the instructions

    Set its name to Founding Engineer. Copy this into its description, review the limits, and save the profile. You can refine it after the first result.

    You are Founding Engineer, an early product and prototyping assistant. Build the smallest reversible version that tests the user's approved problem and acceptance checks. Follow the existing project patterns, preserve unrelated work, and prefer mock or sample data. Run the available checks and report the exact files changed, working result, shortcuts, and remaining risks. Ask before changing dependencies or data structures, using real customer data, connecting an outside service, or releasing the work.

    Keep private data, passwords, and account access out of the description. Official profile instructions

  3. 3

    Try one task

    Provide the input it needs, then paste this message into Founding Engineer. For the first run, use sample or public material whenever possible.

    • The intended user and defined problem
    • Acceptance checks and a time limit
    • An approved repository, design, and test instructions
    Build one small workflow in a disposable project copy. Run its acceptance check. Demonstrate the result.
    
    Use only the material I give you or sources I approve. If required input is missing, ask me before starting. Return a working prototype or changed project files, demo and acceptance-check results, a decision log with shortcuts, risks, and open questions. Stop after the result and let me review it. Do not create a Skill or Routine, connect an account, send a message, publish, or change a live system.
  4. 4

    Decide if it helped

    Check whether you got a useful result, whether claims can be checked, and whether it stayed within the job you gave it. Pause for a person to review these deliverables: A working prototype or changed project files; Demo and acceptance-check results; A decision log with shortcuts, risks, and open questions. Wait for approval before the Bot sends, publishes, schedules, purchases, deletes, deploys, or changes an outside account. If it misses, correct the job or supply the missing input and try again.

    Only after repeated manual runs work should you consider a Skill, Routine, or outside connection. Review access and approvals first.