pm

Manage issue lifecycles and sprint planning across Sigil.

9|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/dylan-murray/sigil --skill pm-dylan-murray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm
Source: https://github.com/dylan-murray/sigil/tree/main/.claude/skills/pm
Command: npx skills add https://github.com/dylan-murray/sigil --skill pm-dylan-murray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sigil's PM skill centralizes issue lifecycle management and sprint coordination, reducing manual coordination and misalignment across teams.

Core Features & Use Cases

  • Create, update, and close issues with consistent metadata and dependencies to keep the backlog healthy.
  • Plan and track sprint goals with a structured current sprint file and a living index, ensuring predictable delivery.
  • Proactively surface priorities, track progress, and keep .issues/INDEX.md up-to-date after every change.

Quick Start

Plan a new sprint by aligning issues to the sprint goal and updating the index and current sprint.

Frequently Asked Questions about pm

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

FAQPage Schema
How do I manage sprint planning and track issue dependencies in one place?

Sprint planning and issue dependency tracking are managed by applying a structured PM workflow to create, update, and prioritize issues while maintaining a living backlog index and current sprint context.

What is the best way to keep a project backlog healthy and aligned with sprint goals?

A healthy backlog aligned with sprint goals is maintained by centralizing issue lifecycle management, enforcing consistent metadata updates, and validating dependencies after every backlog change.

How do I coordinate the issue lifecycle across multiple teams to prevent misalignment?

Issue lifecycle coordination across teams is handled by centralizing backlog management, enforcing memory and context updates, and proactively surfuring priorities to reduce manual misalignment.

Can I use this for tracking sprint progress and updating the issue index automatically?

Yes, sprint progress tracking and index updates are enforced by the workflow, ensuring the `.issues/INDEX.md` file remains current and the current sprint file reflects predictable delivery after every change.

Does this project management approach work without external issue-tracking tools?

Yes, this approach works independently by managing the issue lifecycle, backlog, and sprint context directly through structured file updates and dependency validation without external issue-tracking dependencies.

When should I not use a centralized workflow for issue and sprint management?

A centralized issue and sprint management workflow should not be used for projects requiring highly informal tracking, as it enforces strict memory, context updates, and dependency validation after every change.