EDD Toolkit

Getting Started

These prompts help you clearly define what you're building before you build it. This is the most important phase. A well-defined problem is half-solved. Spend time here to save significant rework later.

SOP Phase: Phase 1 — Problem Definition

Used in: Course 2 Module 4, Course 3 Module 5

Tool: GenAI.mil for all exercises

Skills: Context Assembly, Task Decomposition

Use this when you have a vague sense that something could be better but haven't crystallized the solution yet. This prompt helps you think through the problem systematically.

Prompt Template

I work as a [YOUR_ROLE] in [YOUR_ORGANIZATION_OR_UNIT_TYPE]. One recurring problem we face is: [DESCRIBE_PROBLEM_IN_2_TO_3_SENTENCES] Help me think through this problem by answering: 1. Who specifically is affected by this problem? 2. How often does this problem occur? 3. What's the current workaround (if any)? 4. What does "solved" look like? 5. What's the simplest possible solution that would help? Don't suggest a solution yet—just help me understand the problem better.

Pro tip: Talk to actual users before filling this out. Your assumption of the problem may not match their reality.

After you understand the problem, use this to generate the formal Problem Definition Document required by the SOP.

Prompt Template

Help me write a Problem Definition Document for a tool I want to build. PROBLEM: [2_TO_3_SENTENCE_DESCRIPTION] TARGET USERS: [WHO_WILL_USE_THIS] CURRENT PROCESS: [HOW_ITS_DONE_NOW] DESIRED OUTCOME: [WHAT_SUCCESS_LOOKS_LIKE] Generate a Problem Definition Document with: 1. Problem Statement (2-3 sentences, specific and measurable) 2. Target Users and estimated count 3. Success Criteria (2-3 measurable metrics) 4. Required Functions (minimum viable - no more than 5) 5. Data Considerations (what information will this tool handle?) 6. Estimated complexity (Simple/Medium/Complex) Keep it concise. This is a 1-page document, not a requirements spec. ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

Generate user stories that capture what different users need from your tool.

Prompt Template

I'm building: [TOOL_NAME_AND_BRIEF_DESCRIPTION] The users are: - [USER_TYPE_1]: [BRIEF_DESCRIPTION_OF_THEIR_ROLE] - [USER_TYPE_2]: [BRIEF_DESCRIPTION_OF_THEIR_ROLE] - [USER_TYPE_3_OR_NA] For each user type, generate 3-5 user stories in this format: "As a [user type], I want to [action] so that [benefit]." Focus on the most common tasks, not edge cases. Prioritize each story as Must Have, Should Have, or Nice to Have.

Be ruthless. A working simple tool beats a broken complex one.

Prompt Template

I'm planning to build: [TOOL_DESCRIPTION_2_TO_3_SENTENCES] My full vision includes these features: [LIST_ALL_FEATURES_YOU_HAVE_THOUGHT_OF] My constraints are: - Development time: [HOURS_AVAILABLE] - Must launch by: [DATE_OR_NA] - Must work for: [MINIMUM_USER_COUNT] For each function in my feature list, analyze: - Is this essential for a minimum viable product, or a "nice to have"? - What's the simplest way to implement this? - What could I cut and still have something useful? Then define the Minimum Viable Product: 1. What is the ONE core problem this solves? 2. What are the 3-5 features that solve that core problem? 3. What can be cut entirely from v1? 4. What can be simplified (e.g., manual instead of automated)? 5. What's the "walking skeleton" I could build in 4 hours to prove the concept? 6. What's a recommended "Version 1" scope I could build in under 20 hours? Be ruthless. A working simple tool beats a broken complex one.

Before delegating a task to AI, use this prompt to evaluate whether it falls inside or outside the AI frontier for your domain. This directly applies the Frontier Recognition skill from Course 1.

Prompt Template

I need to evaluate whether a task is suitable for AI assistance. ## TASK DESCRIPTION [Describe the specific task you want AI to help with] ## DOMAIN CONTEXT [What field/specialty does this task belong to? What expertise is needed to verify the output?] ## EVALUATION CRITERIA For this task, help me assess: 1. **Inside the frontier?** Can AI reliably produce a correct or useful output for this type of task? What evidence supports this? 2. **Outside the frontier?** What aspects of this task require human judgment, institutional knowledge, or real-world verification that AI cannot provide? 3. **Verification difficulty:** How hard is it to check if the AI output is correct? Can someone without deep expertise verify it, or does it require a subject matter expert? 4. **Risk of undetected errors:** If the AI gets something wrong, how likely is it that the error would go unnoticed? What would the consequences be? 5. **Recommended approach:** Based on the above, should I: - Delegate fully to AI (inside frontier, easy to verify) - Use centaur mode (human designs, AI executes, human verifies) - Use cyborg mode (continuous human-AI collaboration) - Keep this task fully human (outside frontier or high-risk errors) ## OUTPUT FORMAT Provide a clear recommendation with reasoning for each criterion.

When to use this: Run this before starting any new AI-assisted task, especially in unfamiliar territory. The biggest risk with AI isn't getting a wrong answer — it's not knowing you got a wrong answer. This check helps you spot tasks where AI errors would be hard to catch.

Before You Build

These prompts help you identify compliance requirements before you build. They help you think through compliance—they don't replace consultation with your Privacy Officer, Cybersecurity Office, or Legal. When in doubt, ask the professionals.

SOP Phase: Phase 2 — Compliance Review

Used in: Course 1 Module 4, Course 4 Module 4

Tool: GenAI.mil (CUI-authorized; describe data types and field names, not actual CUI values); consult your Privacy Officer and Cybersecurity Office

Skills: Quality Judgment

Before building, understand if your data fields constitute PII and what that means for your project. References NIST 800-53 privacy controls.

Prompt Template

I'm building a tool that will collect/store/process the following data: [LIST_ALL_DATA_FIELDS_YOUR_TOOL_WILL_HANDLE] (List field names and data types only — do not paste actual data values or records into this prompt.) For each field, tell me: 1. Is this PII (Personally Identifiable Information)? 2. If yes, what category (direct identifier, quasi-identifier, sensitive)? 3. Could this field be combined with others to identify an individual? Then summarize: - Total PII fields identified - Whether a Privacy Impact Assessment is likely required - Recommended data minimization (fields I could remove or anonymize) Reference current DoW privacy directives (DoWI 5400.11) and NIST 800-53 privacy controls for PII definitions. (Consult your unit Privacy Officer or Cybersecurity Office for guidance on specific requirements.)

Walk through the standard PIA threshold questions to determine your privacy review requirements.

Prompt Template

Answer these questions about my planned tool to determine PIA requirements: Tool description: [TOOL_DESCRIPTION_2_TO_3_SENTENCES] 1. Will it collect PII from individuals? [YES_OR_NO] 2. If yes, from how many individuals? [APPROXIMATE_NUMBER] 3. Will it create a new database/repository containing PII? [YES_OR_NO] 4. Will PII be retrievable by individual identifier? [YES_OR_NO] 5. Will it share PII with external parties? [YES_OR_NO] 6. Will it use PII for a new purpose not covered by existing SORN? [YES_OR_NO] 7. Will it collect PII about minors (under 18)? [YES_OR_NO] 8. Will it collect sensitive PII (SSN, financial, medical, biometric)? [YES_OR_NO] Based on the answers, tell me: - Whether a PIA is likely required - What level of privacy review I need - What I should discuss with the Privacy Officer

Generate a security controls checklist specific to your tool's sensitivity and user base. Considers NIST 800-53 controls and FedRAMP requirements for cloud components.

Prompt Template

I'm building: [TOOL_DESCRIPTION_2_TO_3_SENTENCES] Platform: [POWER_APPS_POWER_AUTOMATE_POWER_BI] Data sensitivity: [DATA_SENSITIVITY_LOW_MEDIUM_HIGH] Users: [INTERNAL_EXTERNAL_BOTH] Generate a security controls checklist: AUTHENTICATION - What authentication is required? - Is CAC/PIV required? - Is MFA required? AUTHORIZATION - What access controls are needed? - What roles/permissions should exist? - Who approves access? AUDIT - What actions must be logged? - How long must logs be retained? - Who reviews logs? DATA PROTECTION - Is encryption at rest required? - Is encryption in transit required? For each control, indicate whether it's automatic (platform provides) or requires implementation. Consider: - NIST 800-53 applicable controls for your data sensitivity level - FedRAMP requirements if deploying to cloud - Section 508 accessibility for any user-facing components

Foundation Layer

These prompts help you design SharePoint lists and Dataverse tables. Get this right and everything else is easier. Get it wrong and you'll be rebuilding. Start minimal—you can add columns, but removing them after data exists is painful.

SOP Phase: Phase 3 — Rapid Prototyping

Used in: Course 2 Module 2, Course 3 Modules 2, 4

Tool: GenAI.mil for data modeling; build in Power Platform

Skills: Context Assembly, Task Decomposition

Turn your functional requirements into data structures (SharePoint lists or Dataverse tables).

Prompt Template

I'm building: [TOOL_DESCRIPTION_2_TO_3_SENTENCES] The tool needs to track/store: [LIST_EVERYTHING_THE_TOOL_NEEDS_TO_REMEMBER] Users need to: [LIST_WHAT_USERS_DO_ADD_RECORDS_UPDATE_STATUS_VIEW_REPORTS_ETC] Data platform: [SHAREPOINT_LIST_OR_DATAVERSE_TABLE] Design the data structure: 1. What SharePoint lists or Dataverse tables do I need? 2. For each list/table, what columns are required? 3. For each column, what data type (text, number, choice, person, date, lookup)? 4. What relationships exist between lists/tables (if multiple)? 5. What columns should be required vs. optional? 6. What default values make sense? Show me the list/table structure in a table format.

Quick design for straightforward single-list/table tools.

Prompt Template

Data platform: [SHAREPOINT_LIST_OR_DATAVERSE_TABLE] I need a SharePoint list or Dataverse table for: [PURPOSE] It should capture: [LIST_ALL_FIELDS_YOU_THINK_YOU_NEED] For this list/table, provide: 1. Recommended list/table name 2. Column definitions in this format: | Column Name | Type | Required | Description | Settings | |-------------|------|----------|-------------|----------| 3. Any calculated columns needed 4. Recommended views (what filtered/sorted views would be useful) 5. Anything I'm missing that I'll probably need later Keep it simple—I can add columns later, but removing them is harder.

Design for more complex tools with multiple entities and relationships.

Prompt Template

I need a data structure for: [TOOL_DESCRIPTION_2_TO_3_SENTENCES] Entities involved: - [ENTITY_1]: [WHAT_IT_REPRESENTS] - [ENTITY_2]: [WHAT_IT_REPRESENTS] - [ENTITY_3_OR_NA] Relationships: - [ENTITY_1] can have many [ENTITY_2] - [OTHER_RELATIONSHIPS] Data platform: [SHAREPOINT_LIST_OR_DATAVERSE_TABLE] Design the SharePoint lists or Dataverse tables: 1. One list/table per entity with all columns defined 2. Lookup columns to establish relationships 3. Any junction lists/tables needed for many-to-many relationships 4. Recommended naming conventions Show me an entity relationship diagram in text format, then the detailed list/table structures.

Design views that make your data actually usable.

Prompt Template

My SharePoint list or Dataverse table contains: [DESCRIBE_LIST_AND_KEY_COLUMNS] Users include: - [USER_TYPE_1]: needs to see [WHAT] - [USER_TYPE_2]: needs to see [WHAT] Design views for this list/table: 1. Default view (what most users see) 2. User-specific views (filtered by current user) 3. Status-based views (e.g., "Pending Items", "Completed") 4. Time-based views (e.g., "This Week", "Overdue") 5. Admin views (everything, for troubleshooting) For each view specify: - View name - Columns shown (in order) - Filter conditions - Sort order - Group by (if applicable)

User Interface

These prompts help you build canvas apps in Power Apps. Focus on working software, not perfect software. Build ugly first, get it working, then make it pretty. Test with real data early.

SOP Phase: Phase 3 — Rapid Prototyping

Used in: Course 2 Module 2, Course 3 Modules 2, 4–5

Tool: GenAI.mil for code generation; copy output into Power Apps

Skills: Task Decomposition, Iterative Refinement

Plan your app structure before writing any formulas.

Prompt Template

I'm building a Power Apps canvas app for: [PURPOSE] Users: [LIST_USER_TYPES_AND_WHAT_THEY_NEED_TO_DO] Data sources: [LIST_SHAREPOINT_LISTS_DATAVERSE_TABLES_OR_OTHER_DATA_SOURCES] Help me plan the app architecture: 1. What screens do I need? 2. What's on each screen (main components)? 3. How do users navigate between screens? 4. What should happen on App.OnStart? 5. What global variables or collections might I need? Draw me a simple screen map showing navigation flow. Keep it minimal—I can add screens later.

Generate gallery formulas including filters and search.

Prompt Template

I need a gallery in Power Apps to display: [WHAT_DATA] Data source: [SHAREPOINT_LIST_OR_DATAVERSE_TABLE] Key columns to show: [LIST_COLUMNS] Users need to: - [VIEW_SELECT_FILTER_SEARCH_WHAT_ACTIONS] Generate: 1. Gallery Items formula (including any filters) 2. Template layout (what goes where in each row) 3. OnSelect formula for the gallery or items 4. Search/filter implementation if needed 5. Empty state handling (what shows when no results) 6. Loading state handling Account for the delegation warning if the list might exceed 2000 items.

Generate form configuration and submit logic.

Prompt Template

I need a form to [CREATE_EDIT_BOTH] records in: [SHAREPOINT_LIST] Columns in the list: [LIST_ALL_COLUMNS_AND_TYPES] Requirements: - Required fields: [LIST_ITEMS] - Fields to hide: [LIST_ANY] - Default values: [LIST_ANY] - Conditional visibility: [ANY_FIELDS_THAT_SHOW_HIDE_BASED_ON_OTHER_VALUES] Generate: 1. Form setup (mode, data source, item) 2. Field configuration for each column 3. Validation approach 4. Submit button OnSelect formula 5. Success/failure handling 6. Reset/cancel behavior

Generate Patch formulas with proper error handling.

Prompt Template

I need to save data to: [SHAREPOINT_LIST] Scenario: [CREATE_NEW_UPDATE_EXISTING_BOTH] Form fields or controls providing values: [LIST_CONTROL_NAMES_AND_THE_COLUMNS_THEY_MAP_TO] Generate: 1. Patch formula for this scenario 2. Error handling (what if save fails) 3. Success feedback (notify user, navigate, reset form) 4. Concurrent editing handling (if applicable) 5. Required field validation before submit 6. Loading state during save Show me the complete OnSelect formula for the submit button.

Implement role detection and conditional UI.

Prompt Template

My app has these user roles: - [ROLE_1]: Can [PERMISSIONS] - [ROLE_2]: Can [PERMISSIONS] - [ROLE_3]: Can [PERMISSIONS] Role information comes from: [HOW_YOU_KNOW_THE_USERS_ROLE_SHAREPOINT_GROUP_LIST_LOOKUP_ETC] Implement role-based access: 1. How to detect current user's role on App.OnStart 2. How to store role in a variable 3. Conditional visibility formulas for controls 4. Conditional navigation (redirect to role-appropriate home) 5. Disabling/enabling controls based on role 6. How to handle users with no assigned role

Automation Layer

These prompts help you build automated workflows. Automation is just "when X happens, do Y." If you can describe the business rule, AI can help you build the flow. Check run history when things don't work.

SOP Phase: Phase 3 — Rapid Prototyping

Used in: Course 3 Module 2 (Centaur), Course 3 Module 4 (Cyborg)

Tool: GenAI.mil for flow logic; CamoGPT for API integrations

Skills: Workflow Integration, Task Decomposition

Describe your business rule, get a flow design.

Prompt Template

I need to automate this process: TRIGGER: When [EVENT_HAPPENS] THEN: [ACTION_1] AND: [ACTION_2] IF: [CONDITION], THEN: [CONDITIONAL_ACTION] Currently this is done: [MANUALLY_PARTIALLY_AUTOMATED_OR_NOT_AT_ALL] Design a Power Automate flow: 1. What trigger should I use? 2. What actions are needed (in order)? 3. What conditions/branches are needed? 4. What data flows between steps? 5. What error handling is needed? 6. What type of cloud flow: instant cloud flow (manual), automated cloud flow (event-triggered), or scheduled cloud flow (time-based)? Draw the flow in text format, then explain each step.

Generate email notification flows with dynamic content.

Prompt Template

I need to send an email when: [TRIGGER_EVENT] Email details: - To: [WHO_SPECIFIC_ADDRESS_DYNAMIC_FROM_DATA_ETC] - Subject: [WHAT_THE_SUBJECT_SHOULD_BE] - Body should include: [LIST_INFORMATION_TO_INCLUDE] - Attachments: [YES_OR_NO_WHAT] Data source: [WHERE_THE_DATA_COMES_FROM] Generate the complete flow: 1. Trigger configuration 2. Any data retrieval steps needed 3. Send email action configuration 4. Dynamic content for subject and body 5. Error handling if email fails 6. How to format the email body nicely (HTML vs plain text) Show me exactly what to put in each field.

Generate complete approval flows with notifications.

Prompt Template

I need an approval workflow: What needs approval: [DESCRIBE] Submitted by: [WHO_SUBMITS] Approved by: [WHO_APPROVES_SINGLE_PERSON_GROUP_OR_CHAIN] Data source: [WHERE_REQUESTS_ARE_STORED] When approved: - [WHAT_HAPPENS] When rejected: - [WHAT_HAPPENS] Design the approval flow: 1. Trigger setup 2. Approval action configuration 3. What information approvers see 4. Approval options (Approve/Reject, custom responses?) 5. Timeout handling (what if no response?) 6. Notification to requester of outcome 7. Status update in source system 8. Multi-level approval if needed

Build flows that run automatically on a schedule.

Prompt Template

I need a flow that runs: [SCHEDULE_FREQUENCY_AND_TIME] When it runs, it should: 1. [ACTION_1] 2. [ACTION_2] 3. [ACTION_3] Data involved: [SOURCES] Design the scheduled cloud flow: 1. Recurrence trigger configuration (exact settings) 2. Time zone considerations 3. Query/filter logic for data 4. Batch processing if needed (looping through items) 5. Summary notification when complete 6. Error handling and alerting 7. How to handle holidays/weekends if relevant Include consideration for flow run time limits.

Add robust error handling to your flows.

Prompt Template

My flow does: [DESCRIBE_FLOW_STEPS] Steps that might fail: - [STEP_1]: Could fail because [REASON] - [STEP_2]: Could fail because [REASON] Implement error handling: 1. Configure run-after settings for error paths 2. Scope blocks for try-catch patterns 3. Retry policies for transient failures 4. Error notification (email/Teams when flow fails) 5. Error logging (write to SharePoint list) 6. Graceful degradation (continue with partial success) 7. How to test error handling Show me the parallel branch structure for error handling.

Build complete API integration flows with authentication and error handling.

Prompt Template

I need to integrate with an external API in Power Automate: API Details: - Endpoint: [BASE_URL_OR_API_NAME] - Authentication: [API_KEY_OAUTH_BASIC_NONE] - Method needed: [GET_POST_PUT_DELETE] - Request format: [JSON_XML_FORM] - Response format: [JSON_XML_OTHER] Integration requirements: - Trigger: [WHEN_SHOULD_THIS_RUN] - What to send: [DATA_TO_SEND] - What to do with response: [STORE_TRANSFORM_TRIGGER_ACTION] - Error handling needs: [RETRY_NOTIFY_FALLBACK] Build me a flow that: 1. **Authenticates** properly (show me how to store credentials securely) 2. **Constructs the request** with proper headers and body 3. **Handles the response** including parsing JSON/XML 4. **Manages errors** with appropriate retry logic and notifications 5. **Logs** important events for troubleshooting Include: - Complete HTTP action configuration - Expression for parsing response - Error handling parallel branch - Any custom connector considerations Note if this requires a premium license.

Reporting Layer

These prompts help you build dashboards and reports. A good dashboard answers questions before they're asked. Focus on what leadership actually needs to know. Less is more—5 clear visuals beats 20 confusing ones.

SOP Phase: Phase 3 — Rapid Prototyping

Used in: Course 3 Module 4 (Training Tracker)

Tool: GenAI.mil for DAX and M code generation

Skills: Context Assembly, Quality Judgment

Start with questions, not data.

Prompt Template

I'm building a dashboard for: [PURPOSE] Audience: [WHO_WILL_USE_THIS_LEADERSHIP_OPERATORS_ANALYSTS_ETC] Data source(s): [WHERE_THE_DATA_COMES_FROM] Help me define dashboard requirements: 1. What questions should this dashboard answer? 2. What metrics matter most to this audience? 3. What time period should be covered? 4. What drill-down capability is needed? 5. How often will this be viewed (real-time, daily, weekly)? 6. What actions should viewers take based on what they see? 7. What comparisons matter (this month vs last, target vs actual)? Prioritize: What are the 3-5 MUST-HAVE visuals vs. nice-to-haves?

Match your data to the best visualization.

Prompt Template

I want to show: [WHAT_YOURE_TRYING_TO_COMMUNICATE] Data involved: - [DIMENSION_1_EG_CATEGORIES_TIME_PERIODS] - [DIMENSION_2_IF_APPLICABLE] - [MEASURE_THE_NUMBER_BEING_SHOWN] What visual should I use? 1. Best visual type and why 2. Alternative options and trade-offs 3. Configuration recommendations (axes, legends, colors) 4. When this visual would be wrong 5. How to handle large numbers of categories 6. Mobile considerations Show me the field mappings (what goes where in the visual).

Generate DAX formulas from plain English descriptions.

Prompt Template

I need a DAX measure that calculates: [DESCRIBE_IN_PLAIN_ENGLISH] My table structure: - Table: [TABLE_NAME] - Columns: [LIST_RELEVANT_COLUMNS] Related tables (if any): - [RELATED_TABLE] linked by [COLUMN] Create the DAX measure: 1. Measure name (following naming convention) 2. Complete DAX formula 3. Explanation of how it works 4. Where to use it (which visuals) 5. Performance considerations 6. Edge cases and how they're handled Test the logic with an example calculation.

Build KPI cards with comparisons and conditional formatting.

Prompt Template

I need a KPI card showing: [METRIC] Requirements: - Current value: [CALCULATION_METHOD] - Comparison to: [COMPARISON_TARGET_PREVIOUS_PERIOD_GOAL_OTHER] - Good/bad indication: [GREEN_WHEN_X_RED_WHEN_Y] Design the KPI card: 1. DAX measure for the current value 2. DAX measure for comparison value 3. Conditional formatting rules 4. Number formatting (decimals, abbreviations) 5. Supporting context (trend arrow, % change) 6. How to handle missing/null data Give me the exact DAX formulas.

Generate M code for complex data transformations in Power Query.

Prompt Template

I need to transform data in Power Query (M): Data source: [EXCEL_CSV_SQL_SHAREPOINT_API_ETC] Current structure: [DESCRIBE_CURRENT_DATA_FORMAT_OR_PASTE_SAMPLE] Desired structure: [DESCRIBE_WHAT_YOU_WANT_IT_TO_LOOK_LIKE] Transformations needed: - [LIST_SPECIFIC_CHANGES: UNPIVOT_MERGE_SPLIT_FILTER_ETC] Help me with: 1. **M Code**: Write the Power Query M code to accomplish this transformation 2. **Step-by-Step**: Explain what each step does 3. **UI Alternative**: Can this be done through the UI? Show me how 4. **Performance**: Are there more efficient ways to do this transformation? 5. **Refresh Considerations**: Any gotchas for scheduled refresh? 6. **Error Handling**: How should I handle nulls, type mismatches, or missing data? If the transformation is complex, break it into a reusable function I can apply to multiple tables.

Fixing Things

These prompts help you fix things that aren't working. Debugging is a skill. The better you describe the problem, the faster you'll solve it. Don't panic—everything is fixable. Change one thing at a time.

SOP Phase: Phase 4 — User Testing

Used in: Course 2 Module 3, Course 4 Module 3

Tool: GenAI.mil or CamoGPT — paste error messages with context (remove any PII, CUI, or sensitive data from error output before pasting)

Skills: Iterative Refinement, Quality Judgment

This is your go-to prompt for any debugging situation.

Prompt Template

I'm trying to: [WHAT_YOU_ARE_TRYING_TO_ACCOMPLISH] I did: [WHAT_ACTION_YOU_TOOK] I expected: [RESULT] I got: [ACTUAL_RESULT] Error message (if any): [PASTE_EXACT_ERROR] Fix it.

Pro tip: The more specific your "I got" section, the faster the fix. Include exact error messages, not paraphrases.

Get specific fixes for Power Apps formula issues.

Prompt Template

My Power Apps formula isn't working. Control type: [BUTTON_GALLERY_FORM_ETC] Property: [ONSELECT_ITEMS_VISIBLE_ETC] Formula: [PASTE_YOUR_FORMULA_EXACTLY] Error message: [PASTE_EXACT_ERROR_OR_NO_ERROR_BUT_DOESNT_WORK] What I'm trying to do: [EXPLAIN_IN_PLAIN_ENGLISH] Relevant data source(s): [SHAREPOINT_LIST_NAME_COLUMNS] Fix this formula. Explain what was wrong and why the fix works.

Understand and resolve delegation warnings properly.

Prompt Template

I'm getting a delegation warning on this formula: [PASTE_FORMULA] Data source: [SHAREPOINT_DATAVERSE_ETC] Approximate rows: [APPROXIMATE_NUMBER] The warning says: [PASTE_WARNING_TEXT] What does this mean, and how do I fix it? 1. Explain what delegation is 2. Why this formula causes the warning 3. Options to fix it 4. Trade-offs of each option 5. What happens if I ignore it Give me a specific rewritten formula if possible.

Debug flows using run history information.

Prompt Template

My Power Automate flow is failing. Flow purpose: [WHAT_IT_SHOULD_DO] Trigger: [WHAT_STARTS_IT] Steps: 1. [STEP_1] 2. [STEP_2] [LIST_YOUR_STEPS] Failing at step: [WHICH_STEP_IF_KNOWN] Error from run history: [PASTE_ERROR_MESSAGE] Inputs to failed step: [PASTE_IF_AVAILABLE] Diagnose and fix this flow.

Translate error messages into plain English and fixes.

Prompt Template

I got this error: [PASTE_THE_COMPLETE_ERROR_MESSAGE] Context: - Platform: [POWER_APPS_AUTOMATE_OR_BI] - What I was doing: [WHAT_ACTION_YOU_TOOK] - Where it appeared: [SCREEN_STEP_OR_LOCATION] Decode this error: 1. What does this error mean in plain English? 2. What typically causes it? 3. How do I fix it? 4. How do I prevent it in the future? Be specific to my context.

Find and fix what's making your solution slow.

Prompt Template

My [POWER_APP_OR_FLOW_OR_REPORT] is running slowly. Symptoms: - What's slow: [LOADING_SAVING_REFRESHING_CALCULATING] - How slow: [APPROXIMATE_TIME] - When it started: [ALWAYS_OR_RECENT_CHANGE] - Intermittent or consistent: [PATTERN] Environment: - Data source: [SHAREPOINT_DATAVERSE_SQL_ETC] - Data volume: [APPROXIMATE_ROW_COUNT] - Concurrent users: [TYPICAL_USER_COUNT] Relevant code/formulas (if applicable): [PASTE_SLOW_FORMULAS_OR_FLOW_ACTIONS] Diagnose this performance issue: 1. **Root Cause Analysis**: What are the most likely causes given these symptoms? 2. **Bottleneck Identification**: How do I pinpoint exactly what's slow? 3. **Quick Wins**: What optimizations can I try immediately? 4. **Architecture Changes**: If quick wins aren't enough, what needs restructuring? 5. **Monitoring**: How do I track performance going forward? Prioritize recommendations by impact and effort required.

Making It Last

These prompts help you create documentation that allows others to use, maintain, replicate, and adapt your tools. Good documentation is what makes your tool institutional capability instead of a burden you leave behind.

SOP Phase: Phase 5 — Documentation

Used in: Course 4 Module 5

Tool: GenAI.mil for drafting; upload existing docs for context (ensure documents are appropriate for the platform's authorization level)

Skills: Context Assembly, Workflow Integration

Documentation for the people who use your tool.

Prompt Template

Generate a User Guide for this tool: TOOL NAME: [NAME] PURPOSE: [ONE_SENTENCE_DESCRIPTION] TARGET USERS: [WHO_USES_THIS] MAIN FUNCTIONS: 1. [FUNCTION_1] 2. [FUNCTION_2] 3. [FUNCTION_3] HOW TO ACCESS: [URL_OR_LOCATION] Generate a User Guide (2-5 pages) including: 1. Overview (what is this, who is it for) 2. Getting started (how to access, first-time setup) 3. How to [FUNCTION 1] - step by step with expected results 4. How to [FUNCTION 2] - step by step 5. How to [FUNCTION 3] - step by step 6. Troubleshooting common issues 7. Getting help (who to contact) Write for a user with no technical background. Include "[INSERT SCREENSHOT]" placeholders where visuals would help. ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

Complete technical documentation for rebuilding the tool.

Prompt Template

Generate a Replication Guide for this tool: TOOL NAME: [NAME] PLATFORM: [POWER_APPS_AUTOMATE_OR_BI] DATA STRUCTURE: [DESCRIBE_OR_LIST_SHAREPOINT_LISTS_AND_COLUMNS] APP SCREENS: [IF_POWER_APPS] [LIST_SCREENS_AND_THEIR_PURPOSE] KEY FORMULAS/LOGIC: [LIST_THE_MOST_IMPORTANT_FORMULAS_OR_BUSINESS_LOGIC] Generate a Replication Guide (10-30 pages) that allows someone to rebuild this tool from scratch: 1. Prerequisites (access needed, accounts, permissions) 2. Data layer setup (SharePoint list creation, column by column) 3. Application layer setup (each screen, each control, each formula) 4. Configuration and settings 5. Testing checklist (how to verify it works) 6. Deployment checklist Include every formula, every setting. Someone following this should produce an identical tool. ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

How to keep the tool running after you're gone.

Prompt Template

Generate a Maintenance Guide for this tool: TOOL NAME: [NAME] DEPENDENCIES: [WHAT_THIS_TOOL_RELIES_ON] DATA SOURCES: [LIST_ITEMS] UPDATE FREQUENCY: [HOW_OFTEN_DATA_OR_CONTENT_CHANGES] Generate a Maintenance Guide (5-10 pages) covering: 1. Regular maintenance tasks (daily/weekly/monthly) 2. User management (add/remove users, permissions) 3. Common issues and fixes (with symptoms, cause, fix) 4. Break-fix procedures (identify problems, troubleshoot, escalate) 5. Dependency updates (what if SharePoint/Power Platform changes) 6. Backup and recovery 7. Handover checklist (for PCS/PCA) ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

Everything your successor needs to know.

Prompt Template

Generate a Handover Document for transferring this tool: TOOL NAME: [NAME] CURRENT MAINTAINER: [NAME] NEW MAINTAINER: [NAME_OR_TBD] HANDOVER DATE: [DATE] Include: 1. Tool overview (purpose, users, current status) 2. Access and credentials (how to access, admin accounts) 3. Documentation locations (where all docs are stored) 4. Pending items (known issues, planned improvements) 5. Key contacts (stakeholders, technical support) 6. Operational notes (gotchas, workarounds, "I wish I'd known...") 7. Handover checklist: - [ ] Access transferred - [ ] Documentation reviewed together - [ ] Test changes made by new maintainer - [ ] Contact info exchanged - [ ] Announced to users ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

Generate professionally formatted documents from scratch or transform existing content into publication-ready documents with custom branding.

Prompt Template

Create or enhance a professional document with custom formatting and branding. CONTENT SOURCE (choose one approach): Option A - NEW CONTENT: [DESCRIBE_WHAT_THE_DOCUMENT_SHOULD_CONTAIN] Option B - EXISTING CONTENT: [PASTE_YOUR_EXISTING_CONTENT_ROUGH_NOTES_OR_DRAFT — ensure content is appropriate for the platform's data authorization level; do not paste CUI into commercial tools] DOCUMENT TYPE: [USER_GUIDE_TECHNICAL_MANUAL_REPORT_MEMO_POLICY_DOCUMENT_OR_OTHER] BRANDING & FORMATTING: - Organization name: [YOUR_ORGANIZATION] - Document title: [TITLE] - Author/Prepared by: [NAME_AND_TITLE] - Date: [DATE_OR_TODAYS_DATE] - Header text: [ANY_REQUIRED_HEADER_OR_CLASSIFICATION_MARKINGS] - Footer text: [REQUIRED_FOOTER_TEXT_OR_STANDARD_PAGE_NUMBERS] - Font preference: [TIMES_NEW_ROMAN_ARIAL_OR_DEFAULT_PROFESSIONAL] - Audience: [WHO_WILL_READ_THIS] - Special requirements: [ANY_SPECIFIC_FORMATTING_NEEDS] ENHANCEMENTS NEEDED (check all that apply): - [ ] Organize into logical sections with clear hierarchy - [ ] Add table of contents - [ ] Format lists and procedures professionally - [ ] Create or improve tables from data - [ ] Add executive summary or overview - [ ] Improve clarity, flow, and readability - [ ] Standardize formatting throughout - [ ] Apply consistent heading styles - [ ] Add appropriate document metadata Generate a publication-quality document with: 1. Professional LaTeX-level typography 2. Consistent heading hierarchy 3. Proper margins (1 inch standard) 4. Professional table formatting if tables are needed 5. Clean bulleted/numbered lists 6. Page numbers with total page count 7. Custom headers and footers as specified 8. Appropriate use of whitespace and visual hierarchy ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

Quality Check

These prompts help with quality assurance review before deployment. QA review is required per the SOP—you cannot review your own work. Your job is to verify it works, check documentation, confirm compliance, and approve or return with feedback.

SOP Phase: Phase 6 — QA Review

Used in: Course 4 Module 4

Tool: GenAI.mil for generating review checklists; human reviewer makes final call

Skills: Quality Judgment, Frontier Recognition

Generate comprehensive test cases for a tool.

Prompt Template

Generate a functionality testing checklist for: TOOL NAME: [NAME] MAIN FUNCTIONS: 1. [FUNCTION_1] 2. [FUNCTION_2] 3. [FUNCTION_3] PLATFORM: [POWER_APPS_AUTOMATE_OR_BI] Create a testing checklist covering: POSITIVE TESTS (expected use): - [ ] Each function with typical input - [ ] Different valid inputs NEGATIVE TESTS (error handling): - [ ] Empty/missing required fields - [ ] Invalid data formats - [ ] Unauthorized access attempt EDGE CASES: - [ ] Very long text inputs - [ ] Special characters - [ ] Empty data source USER EXPERIENCE: - [ ] Can complete tasks without documentation? - [ ] Are error messages helpful? For each test, specify: Input -> Action -> Expected Result ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

Generate the formal QA summary for sign-off.

Prompt Template

Generate a QA Review Summary: TOOL: [NAME] DEVELOPER: [NAME] REVIEWER: [YOUR_NAME] REVIEW DATE: [DATE] TESTING PERFORMED: [SUMMARIZE_WHAT_YOU_TESTED] FINDINGS: Critical: [APPROXIMATE_NUMBER] Major: [APPROXIMATE_NUMBER] Minor: [APPROXIMATE_NUMBER] Observations: [APPROXIMATE_NUMBER] [LIST_EACH_FINDING_BRIEFLY] DOCUMENTATION STATUS: - User Guide: [COMPLETE_INCOMPLETE_OR_MISSING] - Replication Guide: [COMPLETE_INCOMPLETE_OR_MISSING] - Maintenance Guide: [COMPLETE_INCOMPLETE_OR_MISSING] RECOMMENDATION: [ ] APPROVED - Ready for deployment [ ] APPROVED WITH CONDITIONS - [LIST CONDITIONS] [ ] REVISIONS REQUIRED - [LIST REQUIRED CHANGES] [ ] REJECTED - [EXPLAIN WHY] Generate the formal summary for sign-off. ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

Ensure your solution meets accessibility standards before deployment.

Prompt Template

Review my Power Platform solution for Section 508 / WCAG 2.1 AA compliance: Application: [APP_NAME_AND_PURPOSE] Platform: [POWER_APPS_CANVAS_OR_MODEL_DRIVEN_OR_POWER_PAGES] Key screens/features: [LIST_MAIN_SCREENS] Generate a comprehensive accessibility audit: 1. **Color & Contrast**: Check all text meets 4.5:1 ratio, UI elements meet 3:1 2. **Keyboard Navigation**: Can all functions be accessed without a mouse? 3. **Screen Reader Compatibility**: Are all controls properly labeled? 4. **Focus Indicators**: Are focus states visible on all interactive elements? 5. **Form Accessibility**: Do all inputs have associated labels? Are errors announced? 6. **Touch Targets**: Are clickable areas at least 44x44 pixels? 7. **Dynamic Content**: Are updates announced to assistive technology? For each issue found: - Severity (Critical/Major/Minor) - Specific location in the app - How to fix it - Code or property to set Include a checklist I can use for testing with actual assistive technology.

Generate a comprehensive UAT plan for stakeholder testing and sign-off.

Prompt Template

Create a UAT plan for my Power Platform solution: Application: [APP_NAME] Purpose: [WHAT_IT_DOES] Key user roles: [LIST_USER_TYPES] Critical workflows: [LIST_MAIN_PROCESSES] Go-live date: [TARGET_DATE] Generate a comprehensive UAT plan including: 1. **UAT Objectives**: What are we validating? 2. **Test Scope**: What's in/out of scope for UAT? 3. **Entry Criteria**: What must be true before UAT begins? 4. **Test Scenarios**: Create realistic test cases for each workflow - Include happy path and edge cases - Specify test data needed - Define expected results 5. **Tester Assignments**: Which user role tests which scenarios? 6. **Defect Process**: How are issues reported, prioritized, and resolved? 7. **Exit Criteria**: What constitutes UAT success? 8. **Sign-off Template**: Provide a formal sign-off document Format as a document I can share with stakeholders.

Create a regression test suite to validate existing functionality after changes.

Prompt Template

I'm about to deploy changes to my Power Platform solution: Application: [APP_NAME] Changes being deployed: [LIST_CHANGES] Existing functionality that must still work: [LIST_CRITICAL_FEATURES] Integrations: [LIST_CONNECTED_SYSTEMS] Generate a regression testing checklist: 1. **Core Functionality Tests**: Verify unchanged features still work 2. **Integration Tests**: Confirm all connections still function 3. **Data Integrity Tests**: Ensure no data corruption or loss 4. **Permission Tests**: Verify RBAC still correct 5. **Performance Baseline**: Compare before/after response times 6. **Edge Cases**: Test boundary conditions affected by changes For each test: - Step-by-step procedure - Expected result - Pass/Fail checkbox - Notes field Include a rollback decision matrix: what severity of failure triggers rollback?

Generate realistic test data including edge cases and boundary conditions.

Prompt Template

I need test data for my Power Platform solution: Application: [APP_NAME] Data entities: [LIST_TABLES_OR_LISTS_WITH_COLUMNS] Relationships: [DESCRIBE_HOW_ENTITIES_RELATE] Constraints: - PII allowed in test data: [YES_OR_NO] - Realistic data needed: [YES_OR_NO] - Volume needed: [NUMBER_OF_RECORDS_PER_ENTITY] - Edge cases to include: [LIST_SPECIAL_SCENARIOS] Generate: 1. **Test Data Set**: Sample data for each entity 2. **Edge Case Data**: Records that test boundaries (nulls, max lengths, special characters) 3. **Relationship Integrity**: Ensure foreign keys resolve correctly 4. **Data Generation Script**: Power Automate flow or script to generate this data 5. **Reset Procedure**: How to clear and regenerate test data Whether PII is allowed or not, never paste real PII records into this prompt as examples. If PII is not allowed in the test data, use obviously fake but realistic-format data (e.g., "Test User 001" not "John Smith").

Conduct comprehensive security assessment of Power Platform solutions.

Prompt Template

Conduct a security review of my Power Platform solution: Application: [APP_NAME] Platform: [POWER_APPS_POWER_AUTOMATE_POWER_BI] Data handled: [DESCRIBE_DATA_TYPES] Data sensitivity: [PUBLIC_INTERNAL_SENSITIVE_PII_CUI] User base: [INTERNAL_EXTERNAL_BOTH] Review for: 1. **Authentication & Authorization** - How are users authenticated? (AAD, external IdP, anonymous) - Is RBAC properly implemented? - Are there any privilege escalation risks? 2. **Data Protection** - Is data encrypted at rest and in transit? - Are there any data exposure risks in formulas or flows? - Could users access data they shouldn't? 3. **Input Validation** - Are all user inputs validated? - Any injection vulnerabilities (especially in dynamic queries)? 4. **Connector Security** - What connectors are used and what permissions do they have? - Are connection credentials properly secured? - Any overly permissive service accounts? 5. **Sharing & Permissions** - Who has access to edit vs. use the solution? - Are there any oversharing risks? 6. **Audit & Monitoring** - What logging exists? - Would you detect misuse? Provide findings as: CRITICAL / HIGH / MEDIUM / LOW with specific remediation steps.

Sharing Knowledge

These prompts help you teach others how to build. Your job isn't to build everyone's tools—it's to help them build their own. The goal is to create more builders, not more dependencies on you.

SOP Phase: Phases 7–8 — Deployment & Sustainment

Used in: Course 4 Module 5

Tool: GenAI.mil for lesson planning; CamoGPT shared workspaces for team exercises (verify current availability)

Skills: Context Assembly, Workflow Integration

Use when someone is stuck and you want to help without doing it for them.

Prompt Template

Someone is stuck on this problem: THEIR GOAL: [WHAT_THEYRE_TRYING_TO_DO] WHAT THEY'VE TRIED: [THEIR_APPROACH] WHERE THEY'RE STUCK: [SPECIFIC_BLOCK] Generate coaching questions that help them find the answer without me telling them directly: LEAD THEM TO THE ANSWER: - "What do you think [X] does?" - "What happens if you try [Y]?" - "Where does the data come from?" HELP THEM DEBUG: - "What's the error telling you?" - "What's different between when it works and when it doesn't?" - "How could you test that assumption?" BUILD THEIR SKILLS: - "How would you search for this?" - "What prompt could you use to ask AI?" Give me 3-5 questions that will help them solve this themselves.

Use to explain something clearly to a beginner.

Prompt Template

Explain [CONCEPT] to someone new to Power Platform. Their background: [TECHNICAL_NONTECHNICAL_OR_SPECIFIC_ROLE] Their goal: [WHAT_THEYRE_TRYING_TO_DO] Generate an explanation that: 1. Starts with why this matters to them 2. Uses an analogy they'd understand 3. Explains the concept simply 4. Shows a minimal example 5. Points to where they can learn more 6. Gives them one thing to try Avoid jargon. If you must use a technical term, define it. Keep it under 2 minutes of reading time.

Use when someone learning to build tools is frustrated.

Prompt Template

Someone learning to build tools is frustrated: They said: "[WHAT_THEY_EXPRESSED_FRUSTRATION_DOUBT_WANTING_TO_GIVE_UP]" The technical issue: [IF_KNOWN] Generate a response that: 1. ACKNOWLEDGES THE FRUSTRATION Don't dismiss it. Building stuff is hard. 2. NORMALIZES THE EXPERIENCE "Everyone hits this wall. I did too." 3. REFRAMES THE SITUATION "You're not failing, you're learning. This error means you're close." 4. OFFERS CONCRETE HELP Either: specific debugging step, or offer to look together, or suggest taking a break 5. REMINDS THEM OF PROGRESS "Remember when you couldn't [thing they can do now]?" The goal is to get them from "I can't do this" to "I haven't figured this out yet."

Use to prepare for teaching a group.

Prompt Template

I'm teaching a [DURATION] session on [TOPIC]. Audience: [WHO_BEGINNERS_INTERMEDIATE_SPECIFIC_ROLE] Size: [NUMBER_OF_PEOPLE] Setting: [IN_PERSON_VIRTUAL_OR_HYBRID] Available equipment: [COMPUTERS_FOR_HANDS_ON_OR_DEMO_ONLY] Generate a session plan: LEARNING OBJECTIVES: By the end, participants will be able to: 1. [OBJECTIVE 1] 2. [OBJECTIVE 2] 3. [OBJECTIVE 3] AGENDA: [TIME] - [TOPIC] - [METHOD: lecture/demo/hands-on] [Continue for each segment] FOR EACH SEGMENT: - Key points to cover - Demo/example to show - Practice exercise (if hands-on) - Check for understanding COMMON QUESTIONS TO PREPARE FOR: - [QUESTION 1] -> Answer - [QUESTION 2] -> Answer BACKUP PLANS: - If exercise takes longer than expected - If tech doesn't work - If skill levels vary widely ## OUTPUT FORMAT Generate this as a professionally formatted document ready for PDF export. Structure with: - Clear heading hierarchy (H1 for title, H2 for sections, H3 for subsections) - Professional typography and consistent spacing - Proper margins and page break considerations - Headers/footers with document title and page numbers - Clean visual hierarchy with appropriate use of whitespace If you have the capability to generate a PDF directly, please do so. Otherwise, provide the content in a format that can be easily converted to PDF (such as well-structured Markdown or HTML).

No prompts match your search

Getting Started

Before You Build

Foundation Layer

User Interface

Automation Layer

Reporting Layer

Fixing Things

Making It Last

Quality Check

Sharing Knowledge