project-management

Generates PRDs, Jira tickets, sprint plans, roadmaps, and technical specs with templates.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill project-management-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-management
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/skills/project-management
Command: npx skills add https://github.com/amanpal3/SKILLs --skill project-management-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers and team leads spend significant time drafting PRDs, writing Jira tickets, planning sprints, and maintaining roadmaps from scratch, often with inconsistent formats and missing acceptance criteria. ## Core Features & Use Cases - PRD & Spec Generation: Produces structured Product Requirements Documents and technical specs with goals, non-goals, user stories, API designs, and rollout plans. - Ticket & Sprint Workflows: Creates Jira user stories, bug reports, epics, and sprint plans with Fibonacci story point estimation and Definition of Done checklists. - Sprint Context Memory: Maintains a context snapshot of the current sprint goal, velocity, blockers, and scope to keep all outputs consistent across sessions. - Use Case: Ask for a PRD for a new checkout feature, then generate the corresponding Jira epic, child stories with acceptance criteria, and a sprint plan sized to your team's velocity. ## Quick Start Write a PRD and Jira tickets for a new user notification feature planned for the next two-week sprint.

Frequently Asked Questions about project-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a PRD for a new feature?▼

Use the PRD template covering overview, problem statement, goals with success metrics, non-goals, user stories, prioritized requirements, edge cases, and timeline. Defining explicit non-goals is critical to prevent scope creep during development.

How to create Jira tickets with acceptance criteria?▼

The skill generates user stories, bug reports, technical tasks, and epics using Given-When-Then acceptance criteria, story point estimates, priority levels, and epic links. Every ticket includes a Definition of Done before entering a sprint.

What story point scale should I use for sprint planning?▼

Use the Fibonacci scale of 1, 2, 3, 5, 8, and 13 points, where 1 is a trivial change and 8 is a large cross-system task. Tickets estimated at 13 points or higher should be split into smaller stories before sprint commitment.

Does this work with Notion and Slack workflows?▼

Yes, it includes Notion page structures for feature briefs and sprint retrospectives, plus Slack templates for daily standups, sprint kickoff announcements, and release notes. These formats can be pasted directly into the respective tools.

When should a ticket be split before sprint planning?▼

Split any ticket estimated above 8 story points, since large tickets carry hidden complexity and rarely finish within one sprint. Tickets without clear acceptance criteria or dependencies on unresolved blockers should also be refined first.