Add markdown style guidelines to daily-news workflow

[Copilot]

The daily-news workflow generates reports without formatting guidance, leading to inconsistent structure. Added inline style guidelines to normalize report formatting across workflow runs.

Changes

Added "Report Formatting Guidelines" section to .github/workflows/daily-news.md:

• Header hierarchy: Use h3/h4 only (h1/h2 reserved for titles)
• Progressive disclosure: Collapse detailed analysis in <details> tags, keep summaries/headlines/takeaways visible
• Report structure: Brief summary → Key headlines → Trend analysis → Detailed analysis (collapsed) → Additional items (collapsed) → Recommendations
• Design principles: Build trust through clarity, exceed expectations, create delight, maintain consistency

Example structure added to prompt:

<details>
<summary><b>Full News Analysis</b></summary>

[Long detailed content here...]

</details>

Follows patterns from shared/reporting.md and daily-repo-chronicle.md for consistency across reporting workflows.

Original prompt

---

This section details on the original issue you should resolve

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

Workflow File: .github/workflows/daily-news.md
Issue: This workflow generates news 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 news report to maintain proper document hierarchy."

2. Progressive Disclosure

Add instruction: "Wrap detailed news analysis and long article sections in <details><summary><b>Section Name</b></summary> tags to improve readability."

Example:

<details>
<summary><b>Full News Analysis</b></summary>

[Long detailed content here...]

</details>

3. Report Structure

Suggest a structure like:

• Brief summary of top news items (always visible)
• Key headlines with links (always visible)
• Detailed article analysis (in <details> tags)
• Additional news items (in <details> tags)
• Recommendations or takeaways (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, summaries, and insights
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 daily-repo-chronicle for good examples of structured news-style reporting with progressive disclosure.

Agent Task

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

AI generated by Workflow Normalizer

• expires on Jan 31, 2026, 12:23 PM UTC

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

• Fixes [workflow-style] Normalize report formatting for daily-news #11651

---

💡 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.