Normalize report formatting guidelines for daily-team-evolution-insights workflow

[Copilot]

The daily-team-evolution-insights workflow was missing formatting guidelines present in other daily reporting workflows, resulting in inconsistent report structure and document hierarchy.

Changes

• Added formatting guidelines section after Mission directive

  • Header hierarchy rules (h3/### minimum, never h2/h1)
  • Progressive disclosure patterns for detailed breakdowns
  • Report structure template (summary → observations → collapsed details → trends)
  • Airbnb-inspired design principles

• Fixed template header levels

  • Changed all h2 (##) section headers to h3 (###): Key Observations, Emerging Trends, Notable Work, Observations & Insights, Looking Forward
  • Normalized subsection headers to h4 (####) for proper hierarchy

• Added progressive disclosure example showing <details> tag usage for contributor activity breakdowns

Context

The discussion title serves as h1, so report content should start at h3 to maintain proper document hierarchy. This matches patterns in daily-team-status.md and daily-issues-report.md.

Before:

## 🎯 Key Observations
...
## 💡 Emerging Trends

After:

### 🎯 Key Observations
...
### 💡 Emerging Trends

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[workflow-style] Normalize report formatting for daily-team-evolution-insights</issue_title>
<issue_description>### Workflow to Update

Workflow File: .github/workflows/daily-team-evolution-insights.md
Issue: This workflow generates daily insights about team evolution and collaboration patterns but doesn't include markdown style guidelines for proper document hierarchy and progressive disclosure.

Required Changes

Update the workflow prompt to include these formatting guidelines:

1. Header Levels

Add instruction after the "Mission" section (after line 47):

Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy.

The discussion title serves as h1, so all content headers should start at h3:

• Use ### for main sections (e.g., "### Key Observations", "### Development Patterns")
• Use #### for subsections (e.g., "#### Team Dynamics", "#### Innovation & Learning")
• Never use ## (h2) or # (h1) in the report body

Note: The current template (lines 107-120) already starts with ## 🎯 Key Observations which should be changed to ### 🎯 Key Observations.

2. Progressive Disclosure

Add instruction for using collapsible sections:

Wrap detailed sections in <details><summary><b>Section Name</b></summary> tags to improve readability and reduce scrolling.

Use collapsible sections for:

• Individual contributor activity breakdowns
• Detailed commit histories and file change lists
• Full PR/issue/discussion activity logs
• Complete code review conversations

Example:

<details>
<summary><b>Detailed Activity Breakdown</b></summary>

### Individual Contributions

#### `@contributor1`
- 15 commits across 23 files
- 2 PRs merged (feat-x, fix-y)
- 8 code review comments

#### `@contributor2`
- ...

</details>

3. Report Structure

Update the current template structure (starting at line 107) to follow this pattern:

1. Executive Summary (always visible): 2-3 paragraphs with key insights about team evolution
2. Key Observations (always visible): Focus areas, velocity, collaboration, innovation highlights
3. Detailed Activity Analysis (in <details> tags): Per-contributor breakdowns, commit histories
4. Trends & Patterns (always visible): What the activity means for the team's evolution
5. Recommendations (always visible): Actionable suggestions for improvement

Design Principles (Airbnb-Inspired)

The updated workflow should create reports that:

1. Build trust through clarity: Most meaningful insights (patterns, trends, observations) immediately visible
2. Exceed expectations: Connect raw activity to strategic insights about team evolution
3. Create delight: Use progressive disclosure to show supporting data without overwhelming the narrative
4. Maintain consistency: Follow the same patterns as other daily reporting workflows

Example Reference

See workflows like daily-team-status.md (lines 52-97) and daily-issues-report.md (lines 248-334) for excellent examples of structured reporting with header guidelines and progressive disclosure.

Current Template Issues

The existing template in the workflow (lines 107-120) needs these specific fixes:

• Change ## 🎯 Key Observations to ### 🎯 Key Observations (line 114)
• Any other ## headers in the template should be changed to ###
• Add <details> sections for detailed activity breakdowns

Agent Task

Update the workflow file .github/workflows/daily-team-evolution-insights.md to:

1. Add formatting guidelines after the "Mission" section
2. Fix the existing template to use h3 instead of h2
3. Add examples of progressive disclosure for detailed contributor activity

Test the updated workflow to ensure it produces well-formatted insights reports that tell a compelling story about team evolution while keeping supporting data accessible but not overwhelming.

AI generated by Workflow Normalizer

• expires on Feb 4, 2026, 12:26 PM UTC

Comments on the Issue (you are @copilot in this section)

• Fixes [workflow-style] Normalize report formatting for daily-team-evolution-insights #12254

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.