status-report
Produce clear, scannable status reports that communicate progress, risks, decisions needed, and outlook. Use for project updates, weekly/monthly reports, steering committee packs, or any recurring status communication.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- status-report
- description
- Produce clear, scannable status reports that communicate progress, risks, decisions needed, and outlook. Use for project updates, weekly/monthly reports, steering committee packs, or any recurring status communication.
03 SKILL.md 正文
Status Report
Overview
Status reports should answer: Where are we? Are we on track? What needs attention? What decisions are required?
When to Use
- Project or program status updates
- Weekly / bi-weekly / monthly reports
- Steering committee or leadership updates
- Cross-team progress communication
Recommended Structure
- Snapshot (overall status, RAG/health, date)
- Highlights / progress this period
- Key metrics or milestones
- Risks, issues, and blockers
- Decisions needed
- Plan for next period
- Appendix (detail) if required
Principles
- Put the most important information first
- Use consistent status indicators (RAG, trends)
- Separate facts from asks
- Be honest about problems early
- Keep the main view to 1–2 pages when possible
Verification
- [ ] Overall status is obvious in seconds
- [ ] Risks and decisions needed are impossible to miss
- [ ] Progress claims are specific and evidence-based
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.