Practice Observations
Observations of specific engineering use cases, encountered problems, and reported practices extracted from the evidence corpus.
18Evidence
18Assessed
0Pending
39Observations
100%Coverage
Assessment coverage measures evidence records explicitly assessed for practice observations. Assessed evidence may legitimately contain zero observations.
13 practice observations · context
| Company | Specific use case being solved | Problem encountered | Reported practice | Selection condition |
|---|---|---|---|---|
| Cursor | Coordinate multi-day programs containing many stacked pull requests and subagents. | Parallel work needs explicit ownership, bounded context transfer, durable state, and independent verification. | pstack defines coordinator, optional sub-coordinator, worker, and verifier roles; structured state files; queue events; and worker briefs. | contextcoordinationverification |
| Infobip | Continue or reconstruct engineering work across agent sessions. | Important state disappears when it exists only in conversational history. | The workflow externalizes durable state into Git, task state, logs, and other artifacts. | contextlearning |
| Infobip | Carry a coding task from research through planning, task definition, and implementation. | One growing context across the workflow becomes noisy and allows upstream errors to compound into implementation. | Infobip structures work into four phases and repeatedly writes, selects, compresses, and isolates context between phases. | context |
| Infobip | Delegate implementation to fresh coding-agent sessions with sufficient task context. | Fresh sessions need goals, dependencies, relevant code paths, success criteria, and validation methods without relying on conversational history. | Research and planning produce validated artifacts, and task definitions carry goals, dependencies, code paths, acceptance criteria, and validation methods. | contextverification |
| Cursor | Coordinate hundreds of agents building a substantial software system concurrently. | Homogeneous agents make conflicting architectural decisions and spend context on both global planning and local implementation. | Cursor separates planner agents that decompose and delegate goals from worker agents that execute bounded pieces. | contextcoordination |
| Spotify | Give coding agents organizational context about software components before and during engineering work. | Agents need component ownership, documentation, and responsible-team information that is not necessarily present in source files. | Spotify exposes Backstage's software catalog to agents through MCPs and command-line tools. | context |
| Spotify | Find concrete source locations that require changes during a fleet-wide migration. | Knowing the downstream consumer does not identify the actual repository usages that need modification. | Spotify uses Codesearch queries to locate migration targets across its GitHub Enterprise landscape. | context |
| Spotify | Identify repositories affected by a downstream dataset migration. | The migration system must know which repositories consume the changed dataset before an agent can modify them. | Spotify uses Backstage endpoint lineage to identify downstream consumers. | context |
| Gloaguen et al. | Provide coding agents repository-specific instructions, workflow guidance, and tool information. | Agents need repository-specific knowledge, but extra context can be redundant and increase exploration and inference cost without improving task resolution. | The evaluated CTXbench repositories use developer-committed repository context files that agents read and follow during coding tasks. | contexteconomics |
| Lulla et al. | Provide coding agents repository-specific guidance while they execute pull-request tasks. | Agents otherwise need to infer repository-specific instructions during execution, which can increase completion time and generated output. | The evaluated repositories provide a version-controlled root AGENTS.md file as repository-level context for the coding agent. | contexteconomics |
| Spotify | Give different background coding agents instructions they can execute effectively. | A single prompt style did not work equally well across agent architectures. | Spotify tailored prompt structure to the agent, using strict step-by-step prompts for its homegrown agent and outcome-oriented prompts for Claude Code. | context |
| Spotify | Make autonomous background coding runs more predictable. | Additional dynamically fetched context and tools increase dimensions of unpredictability. | Spotify limits tools and hooks, constrains Git and Bash operations, and exposes standardized verification. | contextexecutionverification |
| Spotify | Turn developer requests from Slack or GitHub into background coding work. | The background coding agent needs sufficient task information before it can independently produce a pull request. | An interactive agent gathers task information and hands a resulting prompt to the background coding agent. | contextcoordination |