agentleFS
aws-solutionsaws-solutions/konductor/skills/status-reporting/SKILL.md

status-reporting

Skill11 starsChanged 50 days agoApache-2.0View on GitHub

Generates program status reports for stakeholders. Use for weekly updates, executive summaries, or milestone reviews.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 16
  2. Distinctive:

    No metrics or progress indicators

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Status Reporting

Overview

Generates program status reports in two formats: executive summary (1-page) for leadership and detailed report for program teams. Covers RAG status per workstream, accomplishments, upcoming milestones, blockers, and action items. Pulls data from available project management tools when configured.

Usage

Use this skill when:

  • Producing weekly program status updates
  • Preparing executive summaries for leadership reviews
  • Reporting on milestone completion at phase gates
  • Consolidating status across multiple workstreams

Core Concepts

RAG Status

Rate each workstream: Green (on track, no risks), Amber (at risk, mitigation in progress), Red (off track, escalation needed). RAG must be justified — include the specific reason for Amber/Red and the mitigation or escalation action.

Two Report Formats

Executive Summary (1-page): Overall RAG, 3 key accomplishments, 3 upcoming milestones, top blockers, ask/escalation. No detail — decisions only. Detailed Report: Per-workstream RAG, task-level progress, metrics (velocity, burn-down), full blocker list, action items with owners and due dates.

Data Sources

Pull from available project management tools (Asana MCP if configured): task completion %, sprint velocity, overdue items, blocker tickets. If unavailable, prompt user for: completed items this period, planned items next period, blockers, and risks.

Output Format — Executive Summary

  1. Program Name & Date — report period
  2. Overall RAG — single status with one-line justification
  3. Key Accomplishments — 3-5 bullet points, outcome-focused
  4. Upcoming Milestones — next 2 weeks, with dates and owners
  5. Blockers & Risks — top items with owner and mitigation
  6. Ask / Escalation — what you need from leadership (or "None")

Output Format — Detailed Report

  1. Workstream Status Table — columns: Workstream, RAG, % Complete, Key Update, Next Milestone, Blocker
  2. Accomplishments — per workstream, with links to artifacts/PRs
  3. Metrics — sprint velocity, burn-down trend, scope changes
  4. Action Items Table — columns: Action, Owner, Due Date, Status, Notes
  5. Risks & Issues — link to RAID log (risk-management skill)
  6. Next Period Plan — key deliverables for next reporting period

Quality Gate

CRITICAL (must fix):

  • RAG status without justification
  • Blockers listed without owner or mitigation
  • Report period or date missing

IMPORTANT (should fix):

  • Action items missing due dates
  • No metrics or progress indicators
  • Accomplishments describe activities not outcomes

SUGGESTION:

  • Could add trend arrows (improving/stable/declining) per workstream
  • Could include week-over-week RAG comparison

Present findings as: CRITICAL → IMPORTANT → SUGGESTION. Ask: "Fix these issues? [y/n]" — unless scope_confirmed is true, in which case report all the findings and leave fixing to the caller, without asking.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.