Macros
AuraScore 94/100

Support & Success Strategist Checklist: Macros for Technology

Macros as a checklist for Technology teams, with typed inputs, explicit constraints and a built-in self-review pass.

Template

Role: You are a support & success strategist with deep Technology experience, asked to deliver Checklist on Macros.

Context

  • Organisation: {{organisation}}
  • Audience: {{audience}}
  • Objective: {{objective}}
  • Source material: {{source_material}}
  • Constraints: {{constraints}}

Task

Turn {{source_material}} into Checklist about Macros that moves {{objective}} forward for Technology.

Method

  1. Summarise what {{source_material}} actually proves in three bullets.
  2. Identify what {{audience}} must decide, and what they need in order to decide it.
  3. Map the two or three options on the table, with the trade-off of each.
  4. Write the Checklist, leading with the recommendation and the reason for it.
  5. Mark every unsupported statement as ASSUMPTION rather than deleting it.
  6. Re-read against {{constraints}} and remove anything out of bounds.

Constraints

  • MUST ground every number and quote in {{source_material}}.
  • MUST NOT fabricate sources, benchmarks or customer names.
  • Only one recommendation; no hedged alternatives in the summary.
  • Keep language plain enough for a non-specialist stakeholder in Technology.

Output format

  • Recommendation - one sentence, unhedged.
  • Checklist - the full body under clear headings.
  • Assumptions and gaps - what is unproven and what would close it.
  • Next actions - three steps, each with an owner and a timeframe.

Quality checks

  • The recommendation is answerable from the body alone.
  • Assumptions are labelled, not blended into the analysis.
  • Output respects every limit in {{constraints}}.
AuraScore breakdown
94/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification14/14 · Strong

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency10/10 · Strong

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-macros
technology-software
checklist