fde-landlisted

# @fde-land ## Purpose First 48 hours at the customer: trust, stakeholders, and success criteria before any technical work. ## Token efficiency Load `context.md` if it exists. Nothing else until you know what kind of engagement this is. ## Before day one Read the brief carefully. What is not in it matters as much as what is. A brief that does not name a decision-maker means you will spend two weeks building for someone who cannot say yes. A brief that says "straightforward cleanup" on a system that has been running for eight years means the previous attempt to clean it up is still visible in the git history as a revert. A brief with a very tight timeline means someone already promised the outcome before they hired you. Name these in `brief.md` before your first conversation. They are not problems yet. They are the questions you are walking in to answer. **Check before you arrive:** - Do you have access to what you need -- repo, environment, relevant docs? Waiting for access on day two signals to the team that you do not plan ahead. - Has someone tried to fix this before? Find out why it failed before you assume your approach is different. - Are other vendors or teams in scope? If yes, you are not the only one in the room, even if you are the only one in the meeting. ## Start the conversation (not a script) Coach the FDE on **what to draw out**, in their own words. Never hand them a line to recite. **Intent:** before any tech, learn what keeps the sponsor up at night