[ ] with your specific details. Everything else is ready to go.
ROLE:
Expert prompt engineer and communication strategist.
REQUEST:
Draft a highly structured prompt using the 4-Layer Prompt Framework for a synthetic, high-stakes communication scenario specific to my daily reality.
GOAL:
To transition from vague inputs to intentional, organized prompts and witness how specific constraints actively shape the precision of the output.
CONTEXT:
I need to master structured prompting to eliminate ambiguity in my professional workflows. I frequently deliver complex communications—such as stakeholder briefings, major process changes, or strategic proposals—and need to automate the drafting process while maintaining high-fidelity results.
Before answering, review the attached "AIQ Advantage™ Knowledge Vault" to ensure your logic adheres strictly to our methodologies and frameworks. Avoid using generic definitions of the terms used in that source document.
INSTRUCTIONS:
1. Analyze my attached Job Profile to identify a high-stakes communication task common to my role.
2. Invent a synthetic (fictional) but realistic scenario relevant to that task.
3. Draft a prompt that I can use to generate this communication, structured strictly into the following four blocks:
- Context Layer: Define the background, industry environment, and the AI's specific role.
- Intent Layer: Set clear objectives and the specific impact the message must achieve.
- Constraints Layer: Include strict rules for tone (e.g., empathetic), style (e.g., concise), and compliance or formatting requirements.
- Output Layer: Define the exact format, success criteria, and delivery preferences.
OUTPUT FORMAT:
Provide a single, ready-to-copy, highly structured prompt architecture.
[ ] with your specific details. Everything else is ready to go.
Analyze the prompt architecture you just created. Based on my Experience Profile, identify which of the layers in the 4-Layer Prompt Framework is currently the "weakest link" for a professional at my level. Rewrite that specific layer to improve technical accuracy and better align with my strategic intent.
ROLE:
AI Training Auditor and Collaborative Strategy Analyst.
REQUEST:
Analyze our entire conversation from this session and generate a comprehensive Lab Submission Summary for my instructor to evaluate my progress toward AIQ Certification.
GOAL:
To provide a structured data set that illustrates my growth from "conversational dabbling" to "systematic architecture," mapping my work directly to the AIQ Advantage™ frameworks.
INSTRUCTIONS:
Provide the summary in plain text using these four sections:
1. Participant & Profile Integration
- Role & Context: Summarize the job role and industry context we worked within.
- Profile Usage: Explicitly describe how I utilized my Job Profile and Experience Profile to personalize the AI's output (e.g., "The learner used the Experience Profile to anchor the AI in 15 years of HR expertise").
2. Strategy & Architecture Deconstruction
- Strategic Intent: In 2-3 sentences, summarize the specific business problem or workflow bottleneck I solved.
- 4-Layer Framework Audit: Deconstruct my final or most successful prompt into the 4-Layer Framework: Context, Intent, Constraints, and Output. Identify if any layer was exceptionally strong or initially missing.
- AIQ ROI™ Mapping: Identify which of the 10 Dimensions of AIQ ROI™ (e.g., Speed-to-Insight, Decision Quality, or Time Value) was most impacted by this task.
3. The Growth Gap (Evolution Log)
- Refinement Logic: Provide 3-5 bullet points on how the conversation evolved. Include your (the AI's) perspective on how my specific refinements (tweaking tone, adding constraints) improved your performance.
4. Governance & Competence Check
- Human-in-the-Loop (HITL) Evidence: Note any instances where I challenged your logic, corrected a hallucination, or refined a tone to ensure brand alignment.
- Snippet Readiness: Evaluate if the logic we built today is "Snippet-Ready." Can this prompt architecture be modularized and saved to a Greatest Hits library for the organization?
CONSTRAINTS:
- EXCLUDE the actual final document (email, report, strategy) created. Focus only on the process and mechanics of the collaboration.
- Length: Keep the summary under 1,000 words.
- Tone: Objective and analytical to ensure the reviewer has clean data to process.