Menu

Individual skill

architecture-client-presentation

0upvotes

Present a design to a client so they can make a decision rather than react to a picture — the brief restated, the moves explained against it, the options with their trade-offs, and a specific decision requested. Use when asked to present a design to a client, prepare a design review meeting, present concept options, or when a client keeps changing their mind after sign-off. Produces the presentation structure, the brief-to-design traceability, the options with honest trade-offs, the cost and programme position, and the decision record that makes sign-off stick.

plugins/pm-architecture/skills/architecture-client-presentation/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,542
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top