Expert Advisory Macro Framework and Governance Specification
Architect a governed canned macro library for high-touch advisory engagements, enforcing billing and liability guardrails.
Use this template to create an enterprise macro specification for high-stakes advisory communications. It provides exact phrasing structures, billing capture prompts, and legal risk controls for partner and consultant interactions.
Role: Knowledge Management and Client Success Principal at a tier-one advisory firm.
Context
- Consultancy domain: {{consultancy_domain}}
- Target client tier: {{target_client_tier}}
- Governance framework: {{governance_framework}}
- Time and billing tracking integration: {{time_tracking_integration}}
- Mandatory liability disclaimer requirements: {{liability_clause_requirements}}
Task
Formulate a rigorous Advisory Macro and Canned Communication Specification that empowers consultants in {{consultancy_domain}} to respond swiftly to {{target_client_tier}} inquiries while automating {{time_tracking_integration}} increments and strictly enforcing {{liability_clause_requirements}}.
Method
- Dissect typical asynchronous client queries across {{consultancy_domain}} engagements into core communication archetypes.
- Map mandatory {{liability_clause_requirements}} to each inquiry type, establishing immutable disclaimer boilerplate.
- Integrate automated billing telemetry prompts to ensure usage of any macro logs the appropriate time increment in {{time_tracking_integration}}.
- Design tokenized parameters allowing dynamic insertion of deliverables, milestone dates, and client stakeholders.
- Establish a macro governance lifecycle complying with {{governance_framework}} for quarterly content deprecation and review.
- Formulate anti-hallucination and anti-overpromising checks embedded directly into macro usage guidelines.
- Detail permission matrices distinguishing junior analyst macros from engagement partner sign-off macros.
Constraints
- MUST embed exact syntax for {{liability_clause_requirements}} in all advisory macro bodies without truncation.
- MUST NOT permit the bypass of {{time_tracking_integration}} capture hooks upon macro dispatch.
- Specifications must cover at least four distinct client query archetypes.
- Length must remain comprehensive while maintaining high readability for technical administrators.
Output format
- Macro Library Architecture Overview (System schema, dynamic placeholder dictionary)
- Functional Macro Catalog (4+ complete macro specs with Name, Trigger, Boilerplate Body, Dynamic Placeholders, Time-Capture Metadata)
- Compliance & Risk Guardrail Spec (Integration of {{liability_clause_requirements}} and partner escalation triggers)
- Maintenance and Governance Runbook (Review cadences and auditing under {{governance_framework}})
Self-review
- Confirm {{consultancy_domain}}, {{target_client_tier}}, and {{governance_framework}} are deeply contextualized.
- Check that every macro includes an explicit {{time_tracking_integration}} logging directive.
- Ensure liability disclaimers are written out verbatim in macro templates.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.