Context Pack
Package the information an AI agent needs to build the MVP slice safely.
Key takeaways
- A context pack is the interface between product intent and agentic execution, stopping the agent from inventing the wrong product.
- Cover six sections: goal, product slice, repo map, constraints, acceptance, and verification.
- Make non-goals explicit and scope the work so it fits inside a single sprint.
- The pack passes the quality bar when the agent can locate the right files without guessing and the user path is testable end to end.
Context is the main interface between product intent and agentic execution. A context pack prevents the agent from rediscovering obvious constraints or inventing the wrong product.
Context Pack Contents
| Section | Include |
|---|---|
| Goal | Hypothesis, target customer, decision rule |
| Product slice | Screens, actions, data, copy, non-goals |
| Repo map | Relevant routes, components, APIs, tests |
| Constraints | Design system, auth, analytics, privacy, deadline |
| Acceptance | What must work before the sprint is done |
| Verification | Commands, browser paths, sample data |
Template
# MVP Context Pack
## Hypothesis
...
## Target Segment
...
## Build Scope
- Include:
- Exclude:
## Key Paths
- Route:
- Component:
- API:
- Test:
## Acceptance Criteria
...
## Verification
...Quality Bar
- The agent can identify the right files without guessing.
- The scope can be completed in one sprint.
- The user path is testable end to end.
- Non-goals are explicit.