pm

Coordinate seven-phase SDLC planning and generate PROJECT_BRIEF.md artifacts.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/VitorAndTxr/omni-sw --skill pm-vitorandtxr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm
Source: https://github.com/VitorAndTxr/omni-sw/tree/main/skills/pm
Command: npx skills add https://github.com/VitorAndTxr/omni-sw --skill pm-vitorandtxr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PMs translate business needs into project objectives, identify risks, estimate effort, and own business-level documentation, enabling a smooth handoff from client to development teams.

Core Features & Use Cases

  • Lead planning, requirements gathering, backlog migration, and objective alignment for new projects.
  • Coordinate seven-phase SDLC workflow (Plan, Design, Validate, Implement, Review, Test, Document) with defined artifacts and gates.
  • Facilitate collaboration among PM, PO, TL, Dev, and QA, ensuring approvals and traceability throughout the lifecycle.

Quick Start

Initiate the PM phase by starting a plan to generate the PROJECT_BRIEF.md and guide backlog creation through the seven-phase SDLC workflow.

Frequently Asked Questions about pm

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

FAQPage Schema
How do I translate business needs into actionable software project plans?

To translate business needs into actionable software project plans, use a structured PM workflow to gather requirements, generate a project brief, and build a prioritized backlog for stakeholder alignment.

What is the seven-phase SDLC workflow for project management?

The seven-phase SDLC workflow for project management is a structured lifecycle covering Plan, Design, Validate, Implement, Review, Test, and Document phases, enforcing specific gates and artifact creation at each step.

How do I coordinate backlog creation and requirements validation across teams?

You can coordinate backlog creation and requirements validation by applying a phase-based workflow that facilitates collaboration among PM, PO, TL, Dev, and QA roles, ensuring traceability and formal approvals.

Do I need stakeholder approval before migrating the project backlog?

Yes, stakeholder approval is required before migrating the project backlog, as the workflow enforces decision gates and surfaces stakeholder alignment through structured documentation like the project brief.

When do I need to generate a PROJECT_BRIEF.md for software development planning?

You need to generate a PROJECT_BRIEF.md during the initial planning phase of a new software project to document objectives, identify risks, estimate effort, and enable a smooth handoff to development teams.

What's the best way to manage end-to-end software documentation and phase gates?

The best way to manage end-to-end software documentation and phase gates is using a PM-led workflow that enforces artifact creation and validation checkpoints across the entire development lifecycle.