agentsclimarketplace

Project status brief

Skill ClarentCinematics/Codex-Skills-for-Enterprise/skills/project-status-brief

Install
npx -y skills add ClarentCinematics/Codex-Skills-for-Enterprise --skill project-status-brief

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Standardize project updates into concise status briefs with health, milestones, blockers, risks, owner actions, and escalation needs. Use when Codex needs to synthesize project notes, stakeholder updates, sprint summaries, launch plans, or program status into a leadership-ready brief.

SKILL.md

1.8 KB, as published. Nobody here has run it

Project Status Brief

Workflow

  1. Identify project objective, owner, reporting period, current phase, and target milestone.
  2. Determine health status from evidence: scope, schedule, quality, budget, resourcing, and stakeholder alignment.
  3. Extract completed work, upcoming milestones, blockers, risks, and dependencies.
  4. Convert vague activity updates into outcome-focused status language.
  5. Call out decisions, escalations, or support needed from leadership.

Output Standard

Use this structure by default:

  • Status: Green, Yellow, Red, or Unknown with one-sentence rationale.
  • Objective: what the project is trying to achieve.
  • Progress This Period: outcomes completed, not just activity.
  • Milestones: completed, current, and upcoming milestones.
  • Blockers / Dependencies: owner, impact, and requested support.
  • Risks: risk, probability, impact, mitigation, and trigger.
  • Next Actions: owner, action, due date, and success signal.
  • Leadership Ask: decision, escalation, or resource request if needed.

Rules

  • Use Unknown when health cannot be inferred from the source.
  • Do not soften material risks to make the update sound better.
  • Make escalation asks specific enough that a leader can act.
  • Keep the brief suitable for a dashboard, email update, or operating review.

References

Read references/status-patterns.md when the user asks for RAG scoring, dashboard format, or launch-readiness framing.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.