Skip to content
Moosewave
Bring your assistant

Codex workflows

Make the task concrete enough that a useful change can be reviewed, tested, and handed back without expanding its scope.

Make the next step deliberate.

  1. Write an observable task

    Name the file, requested edit, source facts, and expected output.

  2. Keep authority explicit

    Separate reading, local editing, deployment, and sending.

  3. Review the result

    Inspect the diff and the verified artifact, not only a completion message.

A brief with boundaries.

Update this local email template using only the supplied facts. Preserve merge variables and required links. Show the diff, run available checks, and explain remaining risks. Do not publish or send without a separate instruction.

Read the complete text
Update this local email template using only the supplied facts. Preserve merge variables and required links. Show the diff, run available checks, and explain remaining risks. Do not publish or send without a separate instruction.

Workflow guidance, not a claim of a verified public connector. Confirm connection, workspace, identity, and permissions before using any assistant with an account.

Published designs to start from.

Real entries in the public library. Preview each design, choose its delivery flow, and replace illustrative content with your approved facts.

These are starting points, not a claim of a completed or activated campaign. Studio examples may need structural changes for your use case.

Keep these checks close.

  • This is a reusable workflow guide, not an active Moosewave Codex integration.
  • Do not place production secrets in prompts or public example files.

Talk to Moosewave about your workflow. For technical context, see documentation and security.