HQ / Indigo
Keep this close
The HQ operating rules

How we work in HQ.

Nine rules and three practical workflows for work that stays organized, secure, shared, and easy to continue.

  1. Work in the HQ folder.

  2. Tell HQ the outcome you want.

    You do not need to memorize every command. Describe what you want to accomplish in plain language and HQ will guide you to the right workflow.

  3. Share work so others can see it.

    When you do work, that doesn’t automatically mean everyone can see it. Use /hq-share to give others permission to view it.

    /hq-share the report with [teammate] and give them read permission

  4. Keep secrets out of chat and files.

    Never paste API keys or passwords into a conversation or ordinary document. Store them in HQ Secrets, then grant access only to the people who need it.

    /hq-secrets

  5. Deploy work people need to view.

    Turn a document, report, deck, or app into a live link with HQ Deploy. Use the returned URL when you send the work to someone.

    /deploy

  6. Start clean. Finish with a handoff.

    Begin with a clear session. When the task is finished—or the session starts feeling slow or confused—leave a handoff and continue in a fresh session. Archive completed sessions only after the handoff.

    /startwork/handoff

  7. Send the context, not just “done.”

    Use HQ DM to tell a teammate what you shared, where the source file lives, and what you need from them. DMs reach people who share an active HQ company with you.

    /dm [teammate] and tell them the report is ready

  8. Teach corrections. Report breakage.

    If HQ needs to remember a correction or preference, teach it with Learn. If the product itself is broken, report it with HQ Bug.

    /learn [correction]/hq-bug [issue]

  9. Invite new teammates through HQ.

    Use the new-hire flow so identity, company membership, vault access, and the final connection check happen in the right order.

    /new-hire
Put the rules together

Example workflows.

Each example shows both ways: use slash commands when helpful, or describe the whole outcome in one prompt.

FLOW 01

Share a brief with the team

With slash commands:

/deploy this brief/hq-share the brief with my team and give them read permission/dm my team and tell them the brief is ready

As one prompt: “Deploy the brief, share it with my team, and send them a DM.”

FLOW 02

Take a bigger project from idea to done

With slash commands:

/startwork [company] [prompt]/brainstorm this project/plan the work/run-project/handoff/hq-sync

As one prompt: “For [company], help me brainstorm this project, make a plan, run it, then hand it off and sync the results.”

FLOW 03

Hand work to another teammate

With slash commands:

/handoff/hq-sync/hq-share this work with [teammate] and give them read permission/dm [teammate] and tell them it’s ready

As one prompt: “Please hand this off, make sure it’s synced, share it with [teammate], and send them a DM letting them know it’s ready.”

[company], [prompt], and [teammate] are placeholders—replace them with the real values for your work.

Simple work. Shared work. Finished work.