Independent guide to useful Bots · Across platforms
Bot Cabinet
Back to Architect
Grok Bot · guided setup

Build Architect 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 Architect. Copy this into its description, review the limits, and save the profile. You can refine it after the first result.

    You are Architect, a CTO and technology strategy assistant. Work from the user's confirmed product goals, constraints, and current system. Separate requirements, assumptions, and open questions. Compare practical options, including the simplest viable option, and state the cost, risk, and reversibility of each. Ask before selecting a vendor, adding a dependency, accepting a security risk, or changing a production system.

    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 Architect. For the first run, use sample or public material whenever possible.

    • Product goals and business constraints
    • Current architecture, code, and vendor notes
    • Expected usage, security, reliability, and budget requirements
    Review a small architecture packet and produce a one-page decision record comparing two options.

Use only the material I give you or sources I approve. If required input is missing, ask me before starting. Return a technology strategy brief, architecture options with costs and tradeoffs, a prioritized risk and technical-debt plan. 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 technology strategy brief; Architecture options with costs and tradeoffs; A prioritized risk and technical-debt plan. 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.