Why this category matters Link to heading

The Communicate effectively category focuses on turning unstructured content into reusable artifacts: templates, summaries, diagrams, and tables.

These workflows are high leverage because they reduce coordination friction across teams.

Use cases Link to heading

  • Developers writing templates, summaries, and project artifacts
  • Project managers converting issue discussions into action items
  • Developers who need consistent, reusable communication artifacts from Copilot Chat

The 5 examples in this category Link to heading

  1. Creating templates
  2. Extracting information
  3. Synthesizing research
  4. Creating diagrams
  5. Generating tables

Diagram: Communication transformation pipeline Link to heading

R - - - C - - R - - - - a o e w i r t p s s v u R a M m s e e i u t i s E c e a i s s a l m r s a A t r r n u e m o m u u b D i m k p e a t a c a l M o a d u r n r t l e E n i o t t c o C i u i - d w s h h t h z r z o t i n r e a e e e u e t d e t s t t m e i t a e p p m a a d x p u l g b s t r t a l r l o s t i a e m e s m s p s t s t s s

1) Creating templates Link to heading

Typical scenario: generate a README template with sections for description, installation, usage, and contribution.

Prompt pattern:

Create a README template for a new open-source project that includes sections for:
- project description
- installation instructions
- usage examples
- contribution guidelines
Make it clear and easy to follow.

What to check in output:

  • Includes practical section order and table of contents.
  • Includes commands and code examples.
  • Includes contribution process and license/contact sections.

2) Extracting information Link to heading

Typical scenarios:

  • Summarize a long discussion and extract action items.
  • List open issues with deadlines and priority cues.

Prompt patterns:

Can you summarize the key points and action items from this discussion?

Can you list the open issues assigned to me, along with their deadlines and priorities?

What to check in output:

  • Action items should be explicit and assignable.
  • Deadlines should map to real issue content.
  • No invented issue metadata.

3) Synthesizing research Link to heading

Typical scenario: condense large source material into key trends and insights.

Strong prompt characteristics from the cookbook:

  • Include source title and abstract.
  • Include sectioned body text.
  • Ask for trends, insights, and recommendations.

What to check in output:

  • Distinguishes observed findings from recommendations.
  • Preserves caveats and limitations.
  • Avoids adding unsupported claims.

4) Creating diagrams Link to heading

Typical scenario: ask for Mermaid code for project timelines or flowcharts.

Prompt pattern:

Create a Mermaid Gantt diagram that covers August 1st 2025 to January 31st 2026.
Include 5 phases, each taking 6 weeks, and overlapping equally.

Important implementation detail:

  • Wrap output in a Mermaid fenced block:
```mermaid
...
```

What to check in output:

  • Date boundaries are valid.
  • Durations and overlaps match requirements.
  • Diagram syntax renders correctly where pasted.

5) Generating tables Link to heading

Typical scenario: convert repeated person/team records into markdown tables.

Prompt pattern:

Convert the following information into a markdown table:
<records>

Useful follow-up from the cookbook:

  • Ask for diagram generation from table fields, such as timezone overlap visualization.

What to check in output:

  • Column completeness and alignment.
  • No dropped rows.
  • Consistent formatting and sorting where required.

Cross-cutting best practices for this category Link to heading

  • Specify output format explicitly: markdown template, checklist, table, or Mermaid.
  • For research synthesis, include source text in structured chunks.
  • For discussion extraction, ask for both summary and action items.
  • Review generated text for tone, accuracy, and audience fit.

Worked example Link to heading

Scenario Link to heading

You have raw team notes and need a publishable project update with a table and diagram.

Input notes Link to heading 

Project: Checkout rewrite
- API integration complete
- UI validation incomplete
- Performance benchmark delayed by one week
- Security review scheduled next Tuesday
Owners: Ana (API), Ravi (UI), Mei (Perf), Luis (Security)

Prompt 1 (summary + action items) Link to heading 

Summarize these notes for engineering leadership.
Return two sections: "Status Summary" and "Action Items".
Each action item must include owner and due date placeholder.

Prompt 2 (table) Link to heading 

Convert the action items into a markdown table with columns:
Task, Owner, Status, Due Date, Risk.

Prompt 3 (diagram) Link to heading 

Create a Mermaid flowchart showing dependencies between API, UI, performance, and security review.

Validation checklist Link to heading

  • No task from notes is dropped.
  • Owners are mapped correctly.
  • Diagram syntax renders successfully.
  • Status wording is audience-appropriate.

Key takeaways Link to heading

  • This category is about turning raw collaboration data into reusable artifacts.
  • Explicit output formats dramatically improve consistency.
  • Summaries should produce actionable, verifiable next steps.
  • Diagram and table generation work best with concrete constraints.

References Link to heading