> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryearmark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build in Codex

> Package meeting decisions into Codex-ready engineering tasks

## From conversation to Codex tasks

Hand off the heavy lifting. Earmark packages your decisions into Codex-ready engineering tasks with clear requirements, constraints, and context from the actual discussion.

## How it works

<Frame caption="Codex-ready engineering tasks from the meeting">
  <div
    style={{
  backgroundImage: 'url(https://mintcdn.com/earmark/vNkCE4NL0UOVgfZk/images/background-blue.png?fit=max&auto=format&n=vNkCE4NL0UOVgfZk&q=85&s=8d57271bb6e72c3715e83d97907c438b)',
  backgroundSize: 'cover',
  backgroundPosition: 'center',
  borderRadius: '1rem',
  padding: '4%',
}}
  >
    <div
      style={{
    borderRadius: '0.875rem',
    overflow: 'hidden',
    boxShadow: '0 24px 60px rgba(15, 23, 42, 0.28)',
  }}
    >
      <img src="https://mintcdn.com/earmark/7bmTb55b6UAEQSbk/images/codex.png?fit=max&auto=format&n=7bmTb55b6UAEQSbk&q=85&s=7ef32eba2c0e62c1c7f9c1572f89346d" alt="Artifact showing Codex-ready engineering tasks with requirements, constraints, and implementation context." style={{ width: '100%', display: 'block' }} width="2754" height="1686" data-path="images/codex.png" />
    </div>
  </div>
</Frame>

1. Run a meeting with Earmark recording
2. Use the **Engineering Specs** template or a custom prompt like "Generate Codex-ready tasks for the backend changes we discussed"
3. Earmark produces structured tasks with requirements, constraints, and implementation context grounded in the transcript
4. Feed the output into Codex as your task specification

## Best templates for Codex workflows

* **Engineering Specs**: extracts actionable engineering items with motivation, requirements, and acceptance criteria
* **Ticket Generator**: produces structured, scoped tasks ready for autonomous execution
* **Technical Architecture**: captures system design decisions and constraints that inform implementation

<Tip>
  The more specific the meeting discussion, the better the Codex input. Discussions that cover requirements, edge cases, and constraints produce tasks Codex can execute with less back-and-forth.
</Tip>