Foundation

/ads status

Show current status and the highest-priority blocker

Claude Code
/ads status

Installed as a plugin? The same command is namespaced: /claude-ads:ads status

What it does

A fast readout of where the project stands: profile state, run state, evidence freshness, and the single highest-priority blocker with recovery steps. Pair it with /ads next when you just want to know what to do first.

Use it to

  • Check project health at the start of a working session
  • Find the one blocker standing between you and the next audit or report
  • Confirm the setup profile and data sources are still valid
  • Spot stale evidence or expired claims before they affect a run
  • Ask what to do next with /ads next and get one prioritized answer

How it works

  1. Read project state

    Loads the setup profile, recent run manifests, and control-plane records.

  2. Run narrow deterministic checks

    Uses the same validation machinery as /ads validate, scoped to current state rather than a full release gate.

  3. Check evidence freshness

    Flags expired claims and missing access, demoting stale evidence for the run instead of trusting it.

  4. Rank blockers

    Orders findings so the single highest-priority blocker is unambiguous.

  5. Report with recovery steps

    Returns status, the top blocker, and what to do about it.

Reads & produces

What it reads

  • The current setup profile and project state directory
  • Recent run bundles and their manifests
  • The capability manifest and control-plane freshness records

What it produces

  • A current status summary across profile, runs, and evidence
  • The highest-priority blocker
  • Exact evidence for each failing check
  • Recovery steps ordered by priority

Guardrails

What /ads status will and will not do, by contract. These boundaries are enforced in the skill itself, not left to judgment.

  • Read-only: status never changes project state, profiles, or accounts.
  • Never reports readiness on stale evidence. Expired claims are demoted for the run rather than quietly accepted.
  • Missing tool or source access is surfaced as a blocker with a recovery path, never treated as a successful check.
  • Every blocker comes with exact evidence, so the readout is verifiable rather than an impression.

Questions

What is the difference between /ads status and /ads validate?

Same deterministic machinery, different scope. Status is a quick current-state readout focused on the top blocker, while validate runs targeted checks against a specific contract, run, capability, or release gate.

What does /ads next do?

It answers the prioritization question directly: given the current status, it names the highest-priority blocker and the recovery step to take first.

Related

/ads validateValidate contracts, runs, capabilities, maturity, or release readiness/ads setupCreate the client, account, KPI, privacy, and guardrail profile/ads monitorReview pacing, delivery, tracking, fatigue, policy, and performanceDocumentationInstall, configure, and run Claude Ads end to end.