# Agnostic Planning Skills

> Use when discovering which planning skill or persona to run. Covers PRDs, tasks, tickets, backlog, sprint, retro, status, risks, GitHub issues, and the four personas. Trigger words: planning, PRD, tasks, tickets, estimation, risks, status, backlog, sprint, retrospective, agile, product management.

- Skill: `igmarin/agnostic-planning-skills` (Agent Skill)
- Install (CLI): `npx skillmds@latest add igmarin/agnostic-planning-skills`
- Raw SKILL.md: https://api.skillmd.com/api/skills/igmarin/agnostic-planning-skills/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: igmarin (https://skillmd.com/u/igmarin)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/igmarin/agnostic-planning-skills

---

# Agnostic Planning Skills

Master entry point. Navigate and activate 12 language-agnostic planning skills plus 4 personas.

**Core principle:** Atomic, task-specific instructions that turn AI coding assistants into reliable product collaborators through structured planning, estimation, risk assessment, and execution tracking.

## Quick Reference

| Task | Primary Skill |
|------|---------------|
| **Write a PRD** | `create-prd` |
| **Review a PRD** | `review-prd` |
| **Break down a feature** | `generate-tasks` |
| **Estimate effort** | `estimate-tasks` |
| **Generate tickets** | `plan-tickets` |
| **Prioritize backlog** | `prioritize-backlog` |
| **Plan a sprint** | `plan-sprint` |
| **Retrospective** | `create-retrospective` |
| **Identify risks** | `identify-risks` |
| **Status report** | `generate-status-report` |
| **Clarify requirements** | `requirements-clarifier` |
| **Manage GitHub issues** | `github-issue` |
| **End-to-end planning** | `product-owner` (persona) |
| **Execution tracking** | `project-manager` (persona) |
| **Technical feasibility** | `tech-lead` (persona) |
| **Full delivery cycle** | `delivery-lead` (persona) |

## HARD-GATE

```text
DO NOT generate implementation code, tasks, or tickets without an approved PRD.
DO NOT fabricate estimates, progress, or risks — be honest about uncertainty.
The PRD is the single source of truth for scope — everything flows from it.
```

## Core Process

1. **Scope** → `create-prd` → `review-prd`
2. **Plan** → `generate-tasks` → `estimate-tasks` → `identify-risks`
3. **Prioritize** → `prioritize-backlog` → `plan-tickets`
4. **Issue creation** → (optional) `github-issue`
5. **Sprint** → `plan-sprint`
6. **Execute** → `generate-status-report` → `identify-risks`
7. **Retrospect** → `create-retrospective`
8. **Clarify** → `requirements-clarifier` (if requirements are vague)
9. **Orchestrate** → Use `product-owner`, `project-manager`, `tech-lead`, or `delivery-lead` personas

## Skill Catalog

| Category | Skills |
|----------|--------|
| **PRD** | `create-prd`, `review-prd` |
| **Task Management** | `generate-tasks`, `plan-tickets`, `estimate-tasks` |
| **Backlog** | `prioritize-backlog` |
| **Ceremony** | `plan-sprint`, `create-retrospective` |
| **Execution** | `generate-status-report`, `identify-risks` |
| **Analysis** | `requirements-clarifier` |
| **GitHub Issues** | `github-issue` |

## Personas

| Persona | Focus | Phases |
|---------|-------|--------|
| **product-owner** | Scope & planning | Discovery → PRD → Tasks → Tickets → Sprint |
| **project-manager** | Execution tracking | Estimation → Risks → Tracking → Status Reports |
| **tech-lead** | Technical feasibility | PRD Review → Feasibility → Estimation Quality → Risk Report |
| **delivery-lead** | End-to-end pipeline | Scope → Plan → Prioritize → Sprint → Execute → Retrospect |

## Integration

- **Source of Truth:** `directory.json` (skill registry)
- **Reference:** `docs/reference/skill-catalog.md`, `docs/reference/integration-matrix.md`
- **Persona Workflows:** `docs/persona-guide.md`

