pm-task-analyser

Name: pm-task-analyser
Availability: InStock
Author: Warpcode

Analyze software tickets to produce technical briefs, effort estimates, and implementation checklists.

2|2|Updated Apr 7, 2013

Search Tags:#planning #analysis #estimation #backlog #risk

Ready to run

npx skills add https://github.com/warpcode/dotfiles --skill pm-task-analyser

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-task-analyser
Source: https://github.com/warpcode/dotfiles/tree/main/generic/.config/opencode/skills/pm-task-analyser
Command: npx skills add https://github.com/warpcode/dotfiles --skill pm-task-analyser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes tickets, provides technical briefs, estimates story points, and breaks features into sub-tasks.

Core Features & Use Cases

Technical briefs for impacted areas and risk assessment.
Story point estimation with justification.
Detailed technical checklists for task splitting.

Quick Start

Analyze a ticket to produce a technical brief and a subtask checklist.

Frequently Asked Questions about pm-task-analyser

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

FAQPage Schema

How do I estimate story points for a software feature?▼

Story point estimation breaks down a feature's technical complexity across database, backend, frontend, and testing layers. This Skill analyzes tickets to produce justified estimates by inspecting codebase impact and dependencies, helping teams scope work consistently.

What's the best way to decompose a large task into subtasks?▼

Feature decomposition splits work into categorized technical subtasks with dependencies and verification steps. This Skill generates detailed checklists that map implementation across all affected layers, making task ownership and sequencing clear.

How do I identify technical risks when planning a feature?▼

Technical risk assessment examines which system layers a change touches and what dependencies exist. This Skill produces technical briefs that surface impacted areas and risks upfront, enabling better planning decisions.

Can I use this for backlog grooming and sprint planning?▼

Yes. The Skill analyzes tickets to produce structured outputs—technical briefs, effort estimates, and implementation checklists—that teams use during backlog refinement and sprint planning to make informed capacity and prioritization decisions.

What information do I need to provide for accurate analysis?▼

Ticket analysis requires the feature description, acceptance criteria, and access to the codebase being affected. The Skill inspects these artifacts to determine technical scope, estimate effort, and identify dependencies across layers.