persona-project-manager

Generates phased master plans and staged sprint backlogs from BRD, SAD, SCHEMA.sql, and API specs.

60|12|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ahmedemad3/super-ai-agency-framework --skill persona-project-manager-ahmedemad3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-project-manager
Source: https://github.com/ahmedemad3/super-ai-agency-framework/tree/main/.agent/skills/PM-skill
Command: npx skills add https://github.com/ahmedemad3/super-ai-agency-framework --skill persona-project-manager-ahmedemad3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivers a structured, phased delivery plan for complex software programs by translating rough strategy into a concrete, gated schedule with defined milestones.

Core Features & Use Cases

  • Master planning that creates a phase-based roadmap (MVP to Scaling) and identifies critical dependencies.
  • Sprint-level backlog generation and risk logging tailored for multi-team environments.
  • Release planning and capacity scheduling that align with strategic objectives and stakeholder expectations.

Quick Start

Analyze BRD, Architecture, and API specs to generate a master plan and initial sprint backlog for the project.

Frequently Asked Questions about persona-project-manager

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

FAQPage Schema
How do I generate a phased master plan from BRD and API specs for complex software delivery?

To generate a phased master plan, this project management skill reads BRD.md and API specs to produce a phase-based roadmap from MVP to Scaling, identifying critical dependencies and gated milestones under Artifacts/05_Planning for complex multi-team software delivery.

Can I automatically create sprint backlogs and track risks for a multi-team program?

Yes, you can create sprint backlogs and track risks for a multi-team program. The skill generates staged sprint backlogs and logs risks tailored for two-week sprints, handling dependency management and capacity scheduling across multiple teams.

What is the best way to schedule release planning and align stakeholder communication across multiple teams?

The best way to schedule release planning and align stakeholders is by translating rough strategy into a concrete, gated schedule. This skill aligns capacity scheduling with strategic objectives and stakeholder expectations across multi-team environments.

Does this agile planning approach require architecture documents like SAD.md and SCHEMA.sql to work?

Yes, this agile planning approach requires architecture documents to work effectively. It reads SAD.md, SCHEMA.sql, BRD.md, and API specs as inputs to accurately generate the master plan and initial sprint backlogs for the software project.

How do I structure a two-week sprint delivery plan for a multi-team software project?

You structure a two-week sprint delivery plan by analyzing your project requirements and architecture. The skill outputs planning artifacts that map dependencies, schedule capacity, and sequence staged backlogs specifically for two-week sprint cycles.