client judgment

Managing client expectations during software delivery requires a delicate balance between technical accuracy and professional authority. This skill prevents the common pitfalls of over-promising, accidental admissions of liability, or burying a "yes" in technical jargon. It helps you draft and review communications regarding readiness, bugs, delays, and scope by grounding every response in verified evidence rather than optimistic assumptions.

What it does

• Drafts readiness updates by checking implementation facts against intended use cases to ensure honest status reporting.
• Reviews stakeholder replies to remove accidental commitments, invented dates, or unauthorized scope changes.
• Identifies delivery blockers and translates technical issues into clear business impacts for non-technical recipients.
• Preserves sender authority by maintaining professional boundaries and avoiding defensive or evasive language.
• Structures next steps by distinguishing between firm commitments, current facts, and proposed future actions.

How it works

1. Evidence gathering: The agent inspects supplied facts or code state to distinguish between "local pass" and "client accepted."
2. Decision matching: It selects a response pattern based on whether requirements passed, a blocker exists, or a limitation is present.
3. Commitment audit: The agent strips out any manufactured dates or free work that the user has not explicitly authorized.
4. Voice adaptation: It generates a concise draft under 100 words for chat or a structured report for formal email.

Frameworks & tools

This skill is framework-agnostic and works with any software project context. It integrates with code repositories to verify TODOs, environment states, and deployment logs before drafting.

Why this beats prompting it yourself

Generic LLM prompts often produce overly apologetic or corporate-sounding fluff that can lead to legal or commercial scope creep. This skill enforces strict grounding rules that separate what is actually "done" from what is merely "possible," protecting your time and professional reputation.

Use cases

• Missed deadlines: Explaining a delay due to third-party dependencies without taking undue blame.
• Readiness checks: Telling a founder if a prototype is stable enough for prospect interviews.
• Scope requests: Declining or deferring "quick fixes" that fall outside the current sprint or contract.
• Bug reports: Acknowledging a verified defect while providing a concrete timeline for the next status update.

Known limitations

This skill does not provide legal or HR advice. It cannot authorize project changes, deploy code, or sign commercial agreements. Drafts require user verification of missing facts.