project-pulse-brief
关于
This skill generates concise, stakeholder-ready project status briefs from raw updates. It provides reusable templates and checklists to summarize highlights, risks, and next steps without requiring external integrations. Use it for automating executive portfolio reporting in Markdown format.
快速安装
Claude Code
推荐/plugin add https://github.com/christopheryeo/claude-skillsgit clone https://github.com/christopheryeo/claude-skills.git ~/.claude/skills/project-pulse-brief在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Project Pulse Brief
Overview
Project Pulse Brief is a lightweight playbook for turning raw project status updates into an executive-ready pulse brief. The skill focuses on repeatable steps, reusable checklists, and a template you can copy into any document or collaboration space. No scripts, bots, or external integrations are required.
Quick Start
- Collect weekly status inputs from project leads by reviewing your shared project email thread and the relevant Google Drive folders.
- Open
assets/templates/pulse_brief_template.mdand duplicate it in your preferred editor or knowledge base. - Summarize the latest highlights, watchlist items, risks, and next steps directly from the email and Drive updates.
- Share the completed brief with stakeholders via your usual communication channels (email, workspace doc, meeting deck, etc.).
What This Skill Provides
- Repeatable workflow for consolidating project updates each reporting cycle.
- Editable template that keeps highlights, blockers, and upcoming work in a consistent structure.
- Curation checklist to maintain quality: confirm owner, dates, status, and key decisions before publishing.
What This Skill Does NOT Provide
✗ Automated data ingestion from portfolio tools.
✗ Command-line utilities or runtime scripts.
✗ Direct integrations with chat platforms or email services.
Recommended Workflow
- Skim project email updates and shared Drive docs to capture the latest wins, issues, and upcoming milestones.
- During a short review session, triage updates into highlights, watchlist, and risks so the brief stays focused on executive-ready talking points.
- Populate the markdown template with the agreed priorities. Use callouts or bolding (see template) to emphasize decisions and support requests.
- Capture follow-up actions in a shared tracker so the next brief can close the loop on open items.
Success Criteria
- Every project entry lists owner, current status, recent wins, blockers, and next steps.
- Sponsors can skim the brief and understand portfolio health within two minutes.
- Follow-up actions from the previous pulse are either completed or reprioritized in the new brief.
Roles & Responsibilities
- Brief Curator: Coordinates intake, validates completeness, and drafts the pulse brief.
- Project Leads: Provide weekly updates aligned to the required fields.
- Executive Sponsor: Reviews the brief for alignment and approves distribution.
Guardrails
- Keep the brief under two pages to preserve executive readability.
- Highlight no more than five items per section; link to supplemental docs for deep dives.
- Use neutral, objective tone—avoid speculative language without data backing.
- Document open risks with clear owners and mitigation dates.
Troubleshooting
- Missing information? Send a quick reply-all on the project email thread with a bulleted request for the specific details you need.
- Conflicting updates? Leave a comment in the source Drive doc or schedule a short huddle to resolve the discrepancy before publishing.
- Updates running long? Prioritize the bullets that require decisions and move the rest into linked reference docs.
Related Skills
- set-up-workday: Pair with Project Pulse Brief for a wider view of operational signals plus delivery progress.
- recent-files: Helps locate supporting artifacts referenced in the pulse brief.
Version History
- 1.1.2 (2024-03-13): Simplified the workflow to rely solely on email and Google Drive inputs—no supplemental guides required.
- 1.1.1 (2024-03-12): Removed the project update worksheet in favor of lightweight intake prompts embedded in the configuration guide.
- 1.1.0 (2024-03-11): Simplified into a documentation-first workflow without CLI tooling or chat integrations.
- 1.0.0 (2024-03-09): Initial release with automation scripts.
GitHub 仓库
相关推荐技能
algorithmic-art
元该Skill使用p5.js创建包含种子随机性和交互参数探索的算法艺术,适用于生成艺术、流场或粒子系统等需求。它能自动生成算法哲学文档(.md)和对应的交互式艺术代码(.html/.js),确保作品原创性避免侵权。开发者可通过定义计算美学理念快速获得可交互的艺术实现方案。
subagent-driven-development
开发该Skill用于在当前会话中执行包含独立任务的实施计划,它会为每个任务分派一个全新的子代理并在任务间进行代码审查。这种"全新子代理+任务间审查"的模式既能保障代码质量,又能实现快速迭代。适合需要在当前会话中连续执行独立任务,并希望在每个任务后都有质量把关的开发场景。
executing-plans
设计该Skill用于当开发者提供完整实施计划时,以受控批次方式执行代码实现。它会先审阅计划并提出疑问,然后分批次执行任务(默认每批3个任务),并在批次间暂停等待审查。关键特性包括分批次执行、内置检查点和架构师审查机制,确保复杂系统实现的可控性。
cost-optimization
其他这个Claude Skill帮助开发者优化云成本,通过资源调整、标记策略和预留实例来降低AWS、Azure和GCP的开支。它适用于减少云支出、分析基础设施成本或实施成本治理策略的场景。关键功能包括提供成本可视化、资源规模调整指导和定价模型优化建议。
