project-pm

Plan scope, decompose tasks, and orchestrate cross-role coordination for software projects.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/rktclgh/Codex_Discord_Agents --skill project-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-pm
Source: https://github.com/rktclgh/Codex_Discord_Agents/tree/main/skills/project-pm
Command: npx skills add https://github.com/rktclgh/Codex_Discord_Agents --skill project-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces ambiguity in software project work by turning vague requests into clear, scoped work packets and a detailed plan that can be executed in parallel by multiple roles. It centralizes planning, doc generation, and cross-role coordination, delivering a single coherent status view to the user.

Core Features & Use Cases

  • Notion-based documentation planning and capture
  • Task decomposition, scope definition, acceptance criteria, and risk logging
  • Parallelization planning across PM, developers, QA, and security reviewers
  • End-to-end work log maintenance and decision tracking
  • Clear handoffs and traceability from inception to delivery

Quick Start

Instruct the PM to convert a vague project request into scoped work packets with clear acceptance criteria and cross-role responsibilities.

Frequently Asked Questions about project-pm

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

FAQPage Schema
How do I decompose ambiguous software requests into parallel work packets?

Task decomposition transforms ambiguous software requests into scoped work packets by enforcing explicit problem statements, acceptance criteria, and parallelization across PM, developers, QA, and security reviewers for iterative delivery.

How does cross-role coordination work for planning software development tasks?

Cross-role coordination orchestrates software development by defining explicit scope, acceptance criteria, and risk logging, enabling clear handoffs and traceability between PM, developers, QA, and security reviewers from inception to delivery.

Can I use Notion for software project documentation and knowledge capture?

Yes, Notion-based documentation planning and knowledge capture centralizes software project work by maintaining an end-to-end work log, decision tracking, and detailed specifications for cross-role handoffs.

What is the best way to plan parallel execution for multiple development roles?

Parallelization planning maps scoped work packets to specific roles like developers, QA, and security reviewers, ensuring tasks are executed concurrently while maintaining a coherent status view and traceable work log.

Do I need explicit acceptance criteria before assigning work packets to developers?

Yes, task decomposition requires explicit problem statements and acceptance criteria before assigning work packets to developers, QA, or security reviewers to reduce ambiguity and support iterative delivery.