Add formatting guidelines to daily-team-status workflow

[Copilot]

The daily-team-status workflow lacked structured formatting guidelines present in other reporting workflows like audit-workflows and daily-firewall-report.

Changes

Added "Report Formatting Guidelines" section with:

• Header hierarchy: Use h3+ (issue title serves as h1)
• Progressive disclosure: Wrap verbose sections in <details> tags
• Report structure: Overview and priorities visible, detailed breakdowns collapsed
• Design principles: Clarity, context, progressive disclosure, consistency

Example Structure

### Team Status Overview
Brief summary of team health

### Key Achievements and Blockers
Critical highlights

<details>
<summary><b>Individual Contributor Details</b></summary>

Per-person activity breakdowns

</details>

### Action Items
Prioritized next steps

Recompiled workflow to generate updated lock file.

Original prompt

---

This section details on the original issue you should resolve

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

Workflow File: .github/workflows/daily-team-status.md
Issue: This workflow generates daily team status reports but doesn't include markdown style guidelines

Required Changes

Update the workflow prompt to include these formatting guidelines:

1. Header Levels

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

2. Progressive Disclosure

Add instruction: "Wrap long sections in <details><summary><b>Section Name</b></summary> tags to improve readability and reduce scrolling."

Example:

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

[Long team member details...]

</details>

3. Report Structure

Suggest a structure like:

• Team status overview (always visible)
• Key achievements and blockers (always visible)
• Individual contributor details (in <details> tags)
• Action items and priorities (always visible)

Design Principles (Airbnb-Inspired)

The updated workflow should create reports that:

1. Build trust through clarity: Most important info immediately visible
2. Exceed expectations: Add helpful context, trends, comparisons
3. Create delight: Use progressive disclosure to reduce overwhelm
4. Maintain consistency: Follow the same patterns as other reporting workflows

Example Reference

See workflows like audit-workflows or daily-firewall-report for good examples of structured reporting with progressive disclosure.

Agent Task

Update the workflow file .github/workflows/daily-team-status.md to include the formatting guidelines above in the prompt instructions. Test the updated workflow to ensure it produces well-formatted reports.

AI generated by Workflow Normalizer

• expires on Feb 1, 2026, 12:23 PM UTC

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

• Fixes [workflow-style] Normalize report formatting for daily-team-status #11756

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.