AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Pm Status

skill-wei63w-pm-manager-pm-status · by wei63w

Show governance health, iteration progress, and today's Top3 actionable todos. Primary daily entry.

↗ Repository
— No reviews yet
0 installs
44 views
0.0% view→install

Install

$ agentstack add skill-wei63w-pm-manager-pm-status

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-wei63w-pm-manager-pm-status)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Pm Status? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

User Input

$ARGUMENTS

Flags: --full (deep scan first), --verbose (show medium/low), --focus=iteration.

Outline

  1. Require .pm/config/project.yaml else recommend /pm-init.
  2. If --full, run discover workflow first (read-only modules -> merge).
  3. Aggregate open findings counts by severity; list blocking items.
  4. Build Today's Top3 from state/todo.md (open/in_progress), order: blocking>high, P0>P1, iteration-related first. Suppress resolved/wontfix/done and low-confidence charter findings.
  5. Show charter/outline status and needs_recompare.
  6. Light iteration progress if process.iteration + milestones/REQ exist.
  7. Default hide medium/low unless --verbose (show counts only).
  8. Point the user to .pm/dashboard/index.html (browser) or overview.md (IDE) for the cross-module aggregate (if missing, run pm dashboard or /pm-all).
  9. End with one health sentence + how to /pm-done TODO-xxx.
  10. Required closing: follow templates/commands/_closing.md - always list the Open these links and ask the user to open the dashboard overview.

Done When

  • [ ] Top3 <= 3 items with clear next actions
  • [ ] No secret leakage in output

Shared Workflow (all /pm-* commands)

Follow this order when the command mutates .pm/ state:

  1. Read .pm/config/project.yaml and .pm/config/local.yaml (if missing and command is not init ??recommend /pm-init).
  2. On-demand scan using sources + extra_scan_roots + --path + conversation paste (highest priority for /pm-fix).
  3. Desensitize evidence ??.pm/evidence/scans/{command}-{timestamp}.json (secrets ??***).
  4. Optional charter compare when charter.status != absent (attach confidence).
  5. Incremental merge into module findings.md / todo.md; sync authoritative state/todo.md.
  6. Refresh state/overview.md (include Today's Top3, max 3, blocking+high by default).
  7. Output risk summary + recommended next step (??0 lines). Never auto-write source/SQL/cloud without confirmation.
  1. Closing (required): end the user-facing reply with Summary + Open these links per templates/commands/_closing.md (dashboard and/or architecture overviews). Ask the user to open them.

Design baseline: repo root pm-manager-v2.md (or packaged copy under memory/).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills