protofire-pm-agent

Manage GRC project lifecycle documentation and compliance gate enforcement.

3|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/protofire/Protofire-GRC-Agent-Skill-Suite --skill protofire-pm-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protofire-pm-agent
Source: https://github.com/protofire/Protofire-GRC-Agent-Skill-Suite/tree/main/pm-agent
Command: npx skills add https://github.com/protofire/Protofire-GRC-Agent-Skill-Suite --skill protofire-pm-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill manages the complex administrative and compliance-heavy workflows required for Protofire GRC projects, ensuring that all gate requirements, RACI assignments, and security protocols are strictly followed.

Core Features & Use Cases

  • Lifecycle Management: Automates the tracking of project phases from kickoff to close-out, including gate co-sign requirements.
  • Compliance Enforcement: Validates RACI population, SoD notations, and security baseline documentation.
  • Use Case: Use this agent to verify that a project's Gate G3-A requirements are met, ensuring the PSF is versioned, the RACI is fully populated, and the necessary co-signs are present before proceeding to the next phase.

Quick Start

Initiate the project manager agent to perform a Gate G3-A compliance check for the current project.

Frequently Asked Questions about protofire-pm-agent

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

FAQPage Schema
How do I enforce compliance gate requirements during a project lifecycle?

To enforce compliance gate requirements, you validate RACI population, verify security baselines, and ensure cross-functional co-sign requirements are met before proceeding across project phases.

What is the best way to manage RACI population and SoD notations for GRC projects?

Managing RACI population and SoD notations involves validating adherence to internal policies by tracking project phases from kickoff to close-out and enforcing strict security protocol documentation.

How do I verify security baseline documentation before advancing project phases?

Verifying security baseline documentation requires checking that the project scope is versioned, the RACI is fully populated, and necessary gate co-signs are present before phase advancement.

When do I need to escalate critical security scope changes in a GRC workflow?

Escalating critical security scope changes in a GRC workflow is required when modifications impact internal policy adherence, ensuring proper SoD notations and cross-functional co-sign validations.

Can I automate compliance checks for cross-functional co-sign requirements?

Automating compliance checks for co-sign requirements is supported by validating gate criteria, ensuring the PSF is versioned, and confirming all necessary approvals are documented across project phases.

Does this GRC project management approach handle segregation of duties notations?

Handling segregation of duties notations is a core compliance enforcement feature, validating that internal policies are strictly followed and critical security scope changes are properly escalated.