architecture-client-presentation

Installation
SKILL.md

Architecture Client Presentation

Clients who reopen decisions usually never made one. They were shown a rendering, said they liked it, and nobody wrote down what had been settled. This structures the meeting so each design move is visibly traceable to the brief they agreed, options carry their real trade-offs, and the session ends with named decisions recorded — which is the only thing that makes a sign-off hold.

What This Skill Produces

  • The presentation structure — the order that produces decisions rather than reactions
  • Brief-to-design traceability — each major move shown answering something the client asked for
  • Options with honest trade-offs — what each costs, gains, and gives up, including the one you do not recommend
  • The cost and programme position — where the scheme sits against budget and dates, stated plainly
  • The decision request — the specific decisions needed at this meeting, and what is blocked without them
  • The decision record — what was agreed, what was rejected, and what remains open, issued afterwards

Required Inputs

Installs
1
GitHub Stars
1.5K
First Seen
2 days ago