gteam-project-manager

Convert ambiguous project requirements into executable plans with scoped tasks, owners, and acceptance criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gcampton/GTeam --skill gteam-project-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gteam-project-manager
Source: https://github.com/gcampton/GTeam/tree/main/specialists/project-manager
Command: npx skills add https://github.com/gcampton/GTeam --skill gteam-project-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translate ambiguous requirements and stakeholder expectations into clear, executable project plans that keep work on schedule, visible, and accountable. It reduces scope creep, clarifies ownership, and surfaces risks early so teams can deliver predictable outcomes.

Core Features & Use Cases

  • Project Scoping & Briefs: Create one-page project briefs that define goals, scope, out-of-scope items, stakeholders, assumptions, and constraints.
  • Work Breakdown & Task Templates: Produce WBS, task templates with owners, estimates, dependencies, and acceptance criteria so every leaf task is executable in one day.
  • Scheduling & Sprint Planning: Build milestone schedules, sprint goals, capacity plans, and critical-path analyses to produce realistic timelines.
  • Risk, Issue & Change Management: Maintain risk registers, issue logs, and a formal change request process with escalation rules and remediation plans.
  • Status Reporting & Stakeholder Communication: Generate weekly status reports (RAG), decisions needed, blockers, and commit lists for transparent stakeholder updates.
  • Use Case: Turn a product spec into an 8-week MVP delivery plan with WBS, sprint commitments, owner assignments, acceptance criteria, and a risk register ready for stakeholder sign-off.

Quick Start

Create an 8-week MVP project plan for a mobile app with 2 engineers and 1 designer including WBS, milestones, sprint plan, owner assignments, and a risk register.

Frequently Asked Questions about gteam-project-manager

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

FAQPage Schema
How do I convert ambiguous product requirements into an executable project plan?

A work breakdown structure (WBS) decomposes project scope into manageable leaf tasks that are executable in one day, complete with assigned owners, time estimates, dependencies, and testable acceptance criteria to ensure accurate timeline estimation.

What's the best way to plan sprints and estimate capacity for a software project?

Project status reporting uses RAG (Red, Amber, Green) indicators to highlight progress, blockers, and decisions needed, providing transparent stakeholder communication and maintaining a formal log of project issues and required changes.

Can I create a risk register and change request documentation for project management?

Yes, this approach suits operational and software projects by creating one-page project briefs that define goals, scope, out-of-scope items, stakeholders, and constraints to maintain accountability and predictable delivery timelines.

How do I generate a project brief that prevents scope creep and clarifies ownership?

Project recovery planning addresses timeline threats by maintaining risk and issue registers, applying remediation plans, and utilizing formal change request processes with clear escalation rules to get delivery back on schedule.