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

Group Discussion Reviewer Methodology

skill-aaronartistzhang-afk-dailywork-group-discussion-reviewer-methodology · by aaronartistzhang-afk

用一套严格的"产品组会评审"方法论,在对话里直接评审一份 PRD —— 无需 API key、无需运行任何代码。产出双轴结论(组内准入 / 模拟评审结果)+ P0/P1/P2 问题,并对 P0 严格把关(只有真正阻断审批/安全上线/可衡量/方向/交付的问题才算 P0)。当用户要"评审 PRD / 模拟组会评审 / 上会模拟 / 找 P0 阻断项 / 组内准入判断"但没有可用的 LLM key、或更想要一个可照做的思维框架时使用。English triggers: "review this PRD", "simulate a group/product review", "find P0 blockers", "is this PRD ready", "use the group-discussion review framework".

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-aaronartistzhang-afk-dailywork-group-discussion-reviewer-methodology

✓ 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-aaronartistzhang-afk-dailywork-group-discussion-reviewer-methodology)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
29d 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 Group Discussion Reviewer Methodology? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Group Discussion Reviewer — methodology (no key, inline)

Apply a disciplined product group-discussion review to a PRD directly in the conversation. No API key, no Node, no code execution — you (the agent) perform the review by following the written methodology.

> This is the lightweight sibling of the group-discussion-reviewer engine skill. The > engine runs the same pipeline deterministically (and gates P0s with code) but needs an > OpenAI-compatible key. Prefer the engine when a key is available and fidelity matters; use > this methodology skill when there's no key, or for a quick framework-driven review. > > Honest limitation: without the engine's deterministic P0 gatekeeper, the strictness of > P0 downgrading depends on your judgment. Hold the P0 bar hard.

How to use

  1. Get the PRD body as text/markdown (this skill does not fetch URLs or expand sheets).
  2. Read methodology.md in this folder and execute its 8 phases in order.
  3. Produce exactly the output contract: ## 组内准入, ## 模拟评审结果, ## P0 Blockers,

## P1 Questions, ## P2 Questions, ## P1/P2 Improvement Suggestions.

  1. Respect the mode the user asks for (standard / deep / challenge; default challenge) and

the language (default Chinese).

The core discipline (summary — full detail in methodology.md)

  • Two independent axes: 组内准入 (is it concrete enough to discuss?) vs 模拟评审结果

(would it pass?). A PRD can be admitted and still 不通过.

  • P0 only for four failures: wrong direction/population, unmeasurable success (for a

formal decision), unsafe launch, or non-viable delivery — each with a concrete product bridge. Everything else (stats audit, SLA/QPS/monitoring, tracking schema, release checklist, compliance checklist, naming/icons, missing sections) defaults to P1/P2.

  • A clean PRD has 0 P0. Don't inflate P0 to fill a quota.
  • Blind review: PRD body only; ignore comments/annotations/post-meeting context. Ask

questions, don't answer them — except every P0 must include a concrete revision.

Always read methodology.md before reviewing; it carries the full P0 gate rules, the calibration priors, and the reviewer lenses.

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.

Versions

  • v0.1.0 Imported from the upstream source.