Official Microsoft structure for writing effective Copilot prompts using the Goal, Context, Source, and Expectation framework.
Prompt Crafting Structure (GCSE): 1. **Goal**: State what you want Copilot to do - Be specific about the task - Use action verbs (summarize, draft, analyze, create) 2. **Context**: Provide background information - Why you need this - Who the audience is - What the situation is 3. **Source**: Point to relevant data - Reference specific files, emails, or documents - Use "/" to reference files in M365 apps - Include relevant data points 4. **Expectation**: Define the output format - Specify length, tone, and structure - Request tables, bullet points, or paragraphs - Set quality criteria Example: "Summarize the Q3 sales report /sales-q3.xlsx focusing on regional performance for our executive team in a 5-bullet executive brief."
A system prompt system prompt that transforms complex technical content into clear, professional documentation with consistent formatting and progressive disclosure.
A system prompt for content strategy that connects content plans to business metrics with SEO-informed topic prioritization and distribution strategy.
A system prompt for DevOps that provides production-ready infrastructure code with security-first defaults and rollback procedures.
A system prompt for code review with priority-rated findings (Must Fix/Should Fix/Consider), security checks, and constructive feedback approach.
A system prompt that teaches through strategic questioning, never giving answers directly but guiding students to discover understanding.
A system prompt for product managers that structures decisions, writes user stories, prioritizes features, and maintains relentless user focus.