workspace-governor-agent

Governs workspace defaults, propagates local rules to AGENTS.md, and detects drift.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/harkers/forge-email-server --skill workspace-governor-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-governor-agent
Source: https://github.com/harkers/forge-email-server/tree/main/skills/workspace-governor-agent
Command: npx skills add https://github.com/harkers/forge-email-server --skill workspace-governor-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Govern workspace-level structure, defaults, agent rules, and operational hygiene so new or evolving workspaces stay coherent and aligned with process. Use when creating a new workspace, adding local operating rules, propagating standards, or tightening workspace governance after major changes.

Core Features & Use Cases

  • shape workspace defaults
  • propagate local rules into AGENTS.md or related files
  • keep process guidance aligned with actual usage
  • identify missing governance or drift
  • boundary: This role owns local workspace rules and structure and does not own portfolio prioritisation or project tracking updates. Hand those to portfolio-planning-agent for portfolio/project planning and forge-pipeline-operator-agent for Forge Pipeline record updates.

Quick Start

Initialize a new workspace with governance defaults and propagate standards into AGENTS.md to maintain coherence.

Frequently Asked Questions about workspace-governor-agent

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

FAQPage Schema
How do I enforce workspace governance and keep standards coherent?

To enforce workspace governance, apply governance defaults during new workspace creation and propagate local rules into AGENTS.md. This maintains operational coherence by tracking changes, detecting drift, and providing rationale to keep evolving workspaces aligned.

What is the best way to propagate local operating rules into AGENTS.md?

Propagating local rules into AGENTS.md is handled by applying governance defaults and tracking changes across the workspace. This ensures process guidance stays aligned with actual usage while providing rationale and follow-up suggestions for consistency.

How do I detect drift in evolving workspaces and maintain compliance?

Detecting drift in evolving workspaces is achieved by tracking changes against established governance defaults. The mechanism identifies missing governance, provides rationale for inconsistencies, and offers follow-up suggestions to restore operational coherence and compliance.

Can I use workspace governance automation for portfolio prioritization and project tracking?

Workspace governance automation does not support portfolio prioritization or project tracking. It owns local workspace rules and structure, handing portfolio planning to portfolio-planning-agent and pipeline records to forge-pipeline-operator-agent.

When do I need to apply workspace governance defaults?

Apply workspace governance defaults when creating a new workspace, adding local operating rules, propagating standards, or tightening governance after major changes. This shapes workspace defaults and ensures operational hygiene stays aligned with process.