Design a repo grounding flow before a coding agent proposes changes.

Instruction: Describe how you would make repo grounding a deliberate step in the workflow.

Context: Assesses whether the candidate can design a practical architecture and explain the main tradeoffs. Describe how you would make repo grounding a deliberate step in the workflow.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

I would start with task clarification, then search for likely owning files, relevant symbols, tests, docs, and recent related changes. Before the agent edits anything, it should be able to explain why those artifacts are the right grounding set.

I also want a checkpoint...

Upgrade to view official answer

Related Questions