Atlas / Skills / popup-studio-ai / Pm Discovery

Pm DiscoverySAFE

skills/popup-studio-ai/pm-discovery

bkit Vibecoding Kit - PDCA methodology + Claude Code mastery for AI-native development

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
—
Hosts
—
License
Apache-2.0
Stars
602
01

Overview

bkit Vibecoding Kit - PDCA methodology + Claude Code mastery for AI-native development

Read from source at commit f9b6b0c367f8OBSERVED · 2026-10-14
Advertisement
02

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: pm-discovery
classification: workflow
classification-reason: PM process orchestration independent of model capability evolution
deprecation-risk: none
effort: high
description: |
  PM Agent Team — automated product discovery, strategy, and PRD generation with 4 PM agents (for a single feature). For multi-feature initiatives with shared scope/budget/timeline, use /sprint master-plan which generates a sprint-level PRD via sprint-master-planner agent (v2.1.13).
  Triggers: pm, PRD, product discovery
argument-hint: "[feature]"
user-invocable: true
agents:
  default: bkit:pm-lead
allowed-tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - Bash
  - AskUserQuestion
imports:
  - ${PLUGIN_ROOT}/templates/pm-prd.template.md
next-skill: pdca plan
pdca-phase: pm
task-template: "[PM] {feature}"
---

# PM Agent Team - Product Discovery & Strategy

> Automated PM analysis pipeline: Discovery + Strategy + Research -> PRD
> Based on [pm-skills](https://github.com/phuryn/pm-skills) by Pawel Huryn (MIT License)

## Overview

PM Agent Team provides AI-powered product management analysis for solo developers
and small teams without a dedicated PM. It runs before the PDCA Plan phase to ensure
you're building the right thing.

## How It Works

```
/pdca pm {feature}
     |
     v
PM Lead (fable) - orchestrates
     |
     +-- pm-discovery  --> Opportunity Solution Tree
     +-- pm-strategy   --> Value Proposition + Lean Canvas     [parallel]
     +-- pm-research   --> Personas + Competitors + Market
     |
     v
pm-prd --> Beachhead + GTM + PRD (8-section)
     |
     v
docs/00-pm/{feature}.prd.md
     |
     v
Next: /pdca plan {feature} (PRD auto-referenced)
```

## Included PM Frameworks (8)

| Framework | Agent | Origin |
|-----------|-------|--------|
| Opportunity Solution Tree | pm-discovery | Teresa Torres |
| Value Proposition (JTBD 6-Part) | pm-strategy | Huryn & Abdul Rauf |
| Lean Canvas | pm-strategy | Ash Maurya |
| User Personas (JTBD) | pm-research | JTBD-based |
| Competitor Analysis | pm-research | Strategic positioning |
| Market Sizing (TAM/SAM/SOM) | pm-research | Dual-method |
| Beachhead Segment | pm-prd | Geoffrey Moore |
| GTM Strategy | pm-prd | Product Compass |

## Usage

```bash
# Run PM analysis
/pdca pm my-saas-app

# After PM analysis, continue with PDCA
/pdca plan my-saas-app    # PRD auto-referenced
/pdca design my-saas-app
/pdca do my-saas-app
```

## Requirements

- Agent Teams enabled: `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`
- Project level: Dynamic or Enterprise (Starter not supported)

## PDCA Integration

```
[PM] --> [Plan] --> [Design] --> [Do] --> [Check] --> [Act] --> [Report]
 ^        ^
 new      PRD auto-referenced in Plan
```

When `/pdca plan {feature}` runs after PM analysis:
1. Checks for `docs/00-pm/{feature}.prd.md`
2. If found, reads PRD and uses as context for Plan document
3. Plan document quality is significantly improved with PM-backed data

## Output

PRD document saved to `docs/00-pm/{feature}.prd.md` containing:
- Executive Summary (4-perspective)
- Opportunity Solution Tree
- Value Proposition + Lean Canvas
- User Personas (3) + Competitor Analysis (5) + Market Sizing
- Beachhead Segment + GTM Strategy
- Product Requirements (8-section PRD)
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.

Audited 2026-10-14 · audit v0.4.1 · source sha f9b6b0c367f8full audit observations/trust-audit/skill/popup-studio-ai__pm-discovery.json · Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-14f9b6b0c367f8SAFEB89first audit
05

Questions

What does the Pm Discovery skill do?

bkit Vibecoding Kit - PDCA methodology + Claude Code mastery for AI-native development

Is Pm Discovery safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Pm Discovery access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

How current is this page?

The grade is for one exact copy of the source (f9b6b0c367f8), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement