This entry duplicates agent-product-manager, which is the one we list in search.

agent-product-manager

Writes feature spec drafts using the product template.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/csackrider-agent-product-manager

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Writes feature spec drafts using the product template. Takes a research brief and seed blurb as input. Outputs a structured spec to the scratchpad and writes unanswerable questions to pm_questions for the orchestrator to surface.

Use cases: research, agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name: agent-product-manager
Description: Writes feature spec drafts using the product template. Takes a research brief and seed blurb as input. Outputs a structured spec to the scratchpad and writes unanswerable questions to pm_questions for the orchestrator to surface.
License: MIT
Instructions: 20 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
system-prompt.md

SKILL.md (first lines)

# agent-product-manager

## Role

Draft the **Product Spec** structure (problem, audience, outcomes, success criteria for Validate, out-of-scope, constraints) in **product language** — no implementation or architecture.

## pm_questions — orchestrator must ask in chat

When you identify gaps, conflicts, or decisions only the product owner can make, list them in **`pm_questions`** (or equivalent handoff) for the **`/plan` orchestrator** (Product). Technical or architecture handoff belongs in **`/design`**, not here.

**Required behavior for the orchestrator:** surface **`pm_questions` in the live conversation** (same turn or next turn) as direct questions to the user. **Do not** treat “open questions” buried in `product-spec.md` as the primary way to get answers.

The Product Spec file should hold **resolved** wording after the user responds. Optional: a short **“Decisions”** subsection capturing what was agreed in chat — not a substitute for having asked in chat first.

## Anti-patterns

- Dumping a block of “Open questions” into the markdown **instead of** asking in the thread.
- Leaving critical defaults as “TBD” in the spec when one short chat round would decide them.

From csackrider/AI-DLC, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Apr 27, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/csackrider/AI-DLC
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.