aws-fde-delivery

# AWS FDE Delivery ## Purpose Apply a Forward Deployed Engineer (FDE) delivery model to any AWS engagement: show up with a working system, not a slide deck. An FDE embeds with the problem, builds the thing, and proves it runs on real (or realistically simulated) infrastructure before handing off a recommendation. This skill encodes the mandatory artifact set every AWS deliverable must ship with, the rule for grounding cost claims in real pricing data, and the rule for preferring AWS MCP Servers over raw CLI at the execution layer. This is a delivery contract, not a technical how-to. It governs what "done" means for an AWS engagement deliverable; pair it with the relevant AWS domain skill (serverless, databases, migration, deployment) for the technical implementation itself. ## When to Use - User asks for an AWS solution proposal, architecture recommendation, or POC for a client, prospect, or internal stakeholder. - A background task is scoped to "build and deliver" something on AWS, not just describe it. - Career Ops or portfolio work needs an AWS deliverable that has to survive technical scrutiny (interview take-homes, client pitches, demo requests). - Any output that will be handed to someone else as the basis for a build-vs-buy or architecture decision. ## The Build-First Contract Slideware is not a deliverable. Every AWS engagement ships all five artifacts below, or explicitly marks the ones it couldn't produce and why. Partial delivery is acceptable; silen...