task-manager

Request a sprint plan for a specific module or UC range. The skill loads the project index and existing JIRA backlog, identifies UC coverage gaps, prioritizes tasks with a P0–P3 framework, and outputs sprint folders with epics and stories.

Story points follow a calibration table from 1 SP (trivial config) to 13 SP (full module). A bundled business-analyst skill extracts complexity signals from UCs such as flow steps, alternative flows, and integrations to guide estimation.

Yes, Mode B handles single-UC breakdowns. It reads the target UC, assigns the next sequential epic code, and generates an _EPIC.md plus STORIES.md with assignee roles, SP estimates, priorities, and acceptance criteria checkboxes.

Yes, it always reads the existing JIRA README and UC-to-Epic lookup table before planning. UCs that already have epics are skipped, and gap UCs marked with warnings are prioritized first.

The skill assigns a PENDING story point value instead of guessing and adds a PM note urging the user to refine the UC. This anti-hallucination measure prevents unreliable estimates.

Requests covering more than three modules at once are refused to control token bloat and preserve estimation quality. The skill asks the user to process modules one at a time.