Skip to lesson
Exit
Build It Yourself: Prototyping & Technical Fluency1 / 2

2 min lesson

The ticket is the brief - and where the metric lives

Rebuild the main list in "The ticket is the brief - and where the metric lives", then say what each item changes.

Step 1 of 2

The ticket is the brief - and where the metric livesdescribe the what, not the how

Instrumentation discipline starts upstream of the dashboard, in how you write the work. In an agent-driven team a detailed Jira/Linear/Notion ticket becomes the agent's brief - the structured context that determines output quality, and the new home of what prompt engineering used to be. A good brief states user stories, requirements, data models and UI but deliberately not the implementation steps, leaving the agent to reason about the how.

  • Put the success definition in the brief, not in a follow-up. The same ticket that scopes the feature should name its one primary metric, its guardrails and the events to fire - so measurement ships with the work instead of being bolted on after launch.
  • Let the agent pull the ticket in (MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition.). With an Atlassian or Linear MCP connected, “implement GRAPH-59” is enough: the agent recognizes the Jira ticket, fetches the full issue, plans and builds - so the quality of your brief is doing the work a long prompt used to.
  • Keep data access read-only. Wire data tools (a read-only SQL or Databricks MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition.) so an agent can fetch the numbers to instrument against but can never drop a prod table - least privilege as a default, not an afterthought.
A vague ticket is a vague metric

Describing the what (the behavior, the data model, the success metric) rather than the how is the same discipline that makes a prototype demoable: it forces you to state, up front, what “it worked” means. If you can't put the primary metric and its guardrails in the ticket, you don't yet know what you're building - and the agent, like an engineer, will fill that gap with a guess.