internal-coordination-brief

Name: internal-coordination-brief
Availability: InStock
Author: Flintmere

Summarizes departmental progress and blockers into a weekly coordination brief.

Updated Apr 18, 2026

Search Tags:#planning #dependencies #blockers #coordination #operations #weekly-brief #cross-department

Ready to run

npx skills add https://github.com/Flintmere/flintmere --skill internal-coordination-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: internal-coordination-brief
Source: https://github.com/Flintmere/flintmere/tree/main/.claude/skills/internal-coordination-brief
Command: npx skills add https://github.com/Flintmere/flintmere --skill internal-coordination-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single-page summary of ongoing work, blockers, and dependencies across departments to improve visibility and alignment without dictating actions.

Core Features & Use Cases

Centralized weekly coordination brief across Marketing, Product/Engineering, Design, Compliance, Growth, Data & Intelligence, and Admin/Ops
Surface collisions, shared dependencies, and upcoming deadlines to help leadership plan and allocate resources
Cross-reference department briefs and calendars to maintain accuracy and reduce meetings

Quick Start

Run the coordinator to generate this week's brief and save it to context/admin-ops/coordination/YYYY-MM-DD-week.md.

Frequently Asked Questions about internal-coordination-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I summarize cross-department blockers and dependencies into a single overview document?▼

Summarize cross-department blockers and dependencies into a single overview document by cross-referencing department briefs and calendars to produce a one-page weekly coordination brief highlighting scheduling conflicts and upcoming deadlines.

What is the best way to surface scheduling conflicts across Marketing, Product, and Admin teams for weekly planning?▼

Surface scheduling conflicts across Marketing, Product, and Admin teams by cross-referencing department briefs and calendars, generating a centralized weekly coordination brief that identifies shared dependencies and upcoming deadlines.

How do I generate a weekly coordination brief for cross-department operations?▼

Generate a weekly coordination brief for cross-department operations by running the coordinator with read-only access to department briefs and calendars, outputting a markdown file at context/admin-ops/coordination/YYYY-MM-DD-week.md.

Does generating a cross-department coordination brief require write access to team calendars?▼

Generating a cross-department coordination brief does not require write access to team calendars; it only requires read-only access to department briefs and calendars to accurately surface blockers and dependencies.

Can I use this weekly brief to reduce alignment meetings across departments?▼

You can use this weekly brief to reduce alignment meetings across departments, as it provides a single-page summary of ongoing work and blockers to improve visibility without dictating actions to teams.

What departments are covered by the internal coordination brief?▼

The internal coordination brief covers Marketing, Product/Engineering, Design, Compliance, Growth, Data & Intelligence, and Admin/Ops, surfacing collisions and dependencies across all these areas.