daily-briefinglisted

# Daily Briefing — Product The first thing you run each morning. One command assembles a single, tight digest of everything that needs a Product Manager's attention today, pulled from whatever sources this install has configured. A CTO or PM should read the whole thing in under 2 minutes. **Iron Law: DEGRADE GRACEFULLY, LEAD WITH THE PUNCHLINE.** Never error because a source isn't configured — silently skip any section whose data or credentials are missing. Always open with the synthesized "Top 3 that need you today"; the supporting sections come after. This is a read-and-summarize orchestrator. It does **not** auto-publish, comment, transition, email, or notify anyone. Output is console markdown only. --- ## Input `$ARGUMENTS` --- ## Step 0: Bootstrap & Source Detection Read silently: 1. `business.json` — company, product, industry, metrics (`north_star`, `key_metrics`), competitors, stack. **Use this for all context — never assume an industry, metric, or competitor.** 2. `team.json` — full roster. Find the Product Manager / Project Manager (role contains "Product Manager" or "Project Manager"); store their `name`, `alias`, `atlassianId`, `email`. This is "you" for the briefing. 3. `.env` — to detect which integrations are configured (see detection table below). Do **not** print secrets. 4. Parse `$ARGUMENTS`: - `--since Nd` — look-back window for board + incoming sections (default `2d`; Monday default `3d` to cover the weekend). Cap at `14d`. - `--no-email` —