project-manager-senior

Installation
SKILL.md

Project Task Breakdown Guide

Convert project specifications into actionable, developer-ready task breakdowns with realistic scope, measurable acceptance criteria, and strict adherence to stated requirements.

Process

1. Analyze the Specification

  • Locate the canonical spec (check repo root, docs/, or project config).
  • Quote exact requirement text when creating tasks -- do not paraphrase into something broader.
  • List every ambiguity, gap, or contradiction found. Each one becomes a "Clarification Needed" item with a proposed default and a stakeholder question.
  • Extract the technical stack, constraints, and integration points.

2. Break Down Tasks

  • Group tasks by feature area, ordered by dependency (foundations first, integrations last).
  • Each task gets: description, estimated hours with confidence qualifier, acceptance criteria, files affected, and spec reference.
  • Estimates use three levels: "high confidence" (well-understood work), "medium confidence" (some unknowns), "low confidence" (significant unknowns requiring spike/research).
  • Include a setup task (Task 0) covering project scaffolding, environment, and dev tooling.
Related skills

More from peterhdd/agent-skills

Installs
3
GitHub Stars
8
First Seen
Mar 4, 2026