Skip to content

im-shashanks/claude-plugins / shaktra/skills/shaktra-pm

shaktra-pm

Verified

Product Manager workflow — PRD creation, user research analysis, persona generation, journey mapping, and feature prioritization. Entry point for product definition work.

FileKindSize
SKILL.mdskill md7.1 KB
agent-prompts.mdmarkdown3.4 KB
brainstorm-workflow.mdmarkdown4.9 KB
full-workflow-hypothesis.mdmarkdown5.0 KB
full-workflow-research.mdmarkdown4.8 KB
full-workflow.mdmarkdown3.0 KB
guided-entry.mdmarkdown5.5 KB
journey-workflow.mdmarkdown4.9 KB
persona-workflow.mdmarkdown4.0 KB
prd-workflow.mdmarkdown5.7 KB
prioritization-workflow.mdmarkdown5.6 KB
research-workflow.mdmarkdown5.2 KB
templates/prd-one-page.mdmarkdown1.7 KB
templates/prd-standard.mdmarkdown3.5 KB

templates/prd-one-page.md

View on GitHub
# PRD Template — One Page

Abbreviated PRD template for 2-4 week features. Use for Small tier work or well-understood enhancements that don't require full design docs.

---

```markdown
---
id: PRD-XXX
title: "[Feature Name]"
version: "1.0.0"
status: draft
created: YYYY-MM-DD
updated: YYYY-MM-DD
author: "[Author Name]"
stakeholders:
  - name: "[Name]"
    role: "[Role]"
---

# [Feature Name]

## Problem

[2-3 sentences: What problem? Who has it? Why does it matter?]

## Solution

[2-3 sentences: What are we building? How does it solve the problem?]

## Users

**Primary:** [Who is this for?]

**Not for:** [Who is this explicitly NOT for?]

## Requirements

### Must Have

| ID | Requirement | Acceptance Test |
|---|---|---|
| REQ-001 | [Requirement] | [How to verify] |
| REQ-002 | [Requirement] | [How to verify] |

### Should Have

| ID | Requirement | Acceptance Test |
|---|---|---|
| REQ-003 | [Requirement] | [How to verify] |

### Out of Scope

- [What this does NOT include]

## Success Metrics

| Metric | Target |
|---|---|
| [Metric 1] | [Target value] |
| [Metric 2] | [Target value] |

## Constraints

- **Timeline:** [Delivery date]
- **Technical:** [Key technical constraint, if any]
- **Dependency:** [Key dependency, if any]

## Risks

| Risk | Mitigation |
|---|---|
| [Risk 1] | [Mitigation] |
```

---

## When to Use One-Page vs Standard

| Criteria | One-Page | Standard |
|---|---|---|
| Timeline | 2-4 weeks | 6-8+ weeks |
| Story tier | Small, some Medium | Medium, Large |
| Complexity | Single component | Multi-component |
| Stakeholders | 1-2 | 3+ |
| Integration | Minimal | External APIs, new data models |
| Design doc needed | No | Yes |

If uncertain, start with one-page. Expand to standard if complexity emerges during design.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall