Skip to content
Back to skills

Pm Ownership

ASecurity

Show who owns what across initiatives, gates, drafts, and Beads issues. Surfaces orphaned artefacts (no owner) and over-loaded owners.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsgobash

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add VandanaAjayDubey111/great-pm --skill pm-ownership --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pm Ownership?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pm Ownership
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vandanaajaydubey111-pm-ownership/badge)](https://www.skillsdirectory.com/skills/vandanaajaydubey111-pm-ownership)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pm-ownership
description: "Show who owns what across initiatives, gates, drafts, and Beads issues. Surfaces orphaned artefacts (no owner) and over-loaded owners."
---

## Codex host binding

- Treat references to Claude slash workflows as the equivalently named Codex skill.
- Before delegating to any specialist, read the `great-pm-runtime` skill and the selected packaged role file.
- Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex `spawn_agent` call with that role and a bounded assignment.
- For the spawn tool's `task_name` or `agent_name` identifier, replace canonical role-name hyphens with underscores (`query-refiner-pm` → `query_refiner_pm`). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename.
- Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
- If `spawn_agent` is unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set.
- Resolve bundled paths from the installed GreatPM plugin root.
- Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
- Preserve GreatPM human gates, governance, state, and reporting contracts.


You are the great-pm `$pm-ownership` command. Build an ownership map.

## Parse arguments

- **`--initiative=<slug>`** → scope the map to a single initiative.
- **`--orphans-only`** → only print artefacts with no owner.
- (no flag) → full ownership map across the whole product.

## Pre-flight

```bash
echo "cwd=$(pwd)"
ls .great-pm/PROJECT.md 2>/dev/null && echo "PROJECT_OK" || echo "NO_PROJECT"
```

If `NO_PROJECT` → BLOCKED.

## Operating procedure

0. **Step 0 — refine the user's query** (transparent Mode B). Invoke
   `query-refiner-pm` with `$ARGUMENTS`. The refiner returns:
   ```
   You typed:  <original>

   Refined to: <refined brief>

   What changed: <one line>

   Proceeding with refined. Reply "use original" to override.
   ```
   Use the **refined** version as the brief for subsequent steps UNLESS
   the user replies "use original". Log the refinement to
   `.great-pm/refinements/$(date +%Y-%m-%d).log`. This wiring is
   universal across great-pm commands per the gate-policy: explicit
   discipline — you make the user's leverage visible while preserving
   their ability to override.

1. Read `.great-pm/PROJECT.md` and parse the "Active initiatives" block —
   each row should have an `owner:` field.

2. List all drafts in `.great-pm/drafts/` — each markdown file should have a
   front-matter `owner:` or `author:` field. Files without one are
   **orphans**.

3. List open gates: `bd list --label gate --status open` — each Beads
   issue has an assignee.

4. Compile the map:

   ```
   == Ownership map ==

   Initiative: <slug>
     Owner: <name>
     Stage: <discover|strategize|prioritize|define|launch|measure>
     Drafts:
       - <draft-1>  (owner: <name>)
       - <draft-2>  (orphan)
     Gates:
       - bd-<id>  gate:<type>  assignee: <name>
   ```

5. End with a summary line:
   ```
   <I> initiatives | <D> drafts (<O> orphans) | <G> open gates | <U> distinct owners
   Over-loaded: <name> (owns <N> artefacts)
   ```

6. If `--orphans-only`, print only the orphan rows.

## Reporting

- **DONE**: `DONE: $pm-ownership — <I> initiatives, <D> drafts (<O> orphans), <G> gates mapped.`
- **BLOCKED**: missing PROJECT.md / Beads unavailable. tried + failed_because + need.

## Notes

- Ownership is metadata. If a draft has no `owner:` field, that's not a
  silent bug — surface it so the user assigns it.
- "Over-loaded" warning fires when one person owns >3 in-flight artefacts.

Files in this skill

  • SKILL.md3.7 KB
  • agents/openai.yaml225 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.