forge-wordpress-suite-agent

Coordinate ForgeWordPress plugin boundaries and shared-foundation contracts across the monorepo.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Govern ForgeWordPress suite work across bounded plugins, shared foundation, hooks/contracts, admin UX, and release coherence. Use when planning, reviewing, implementing, or coordinating work in the ForgeWordPress monorepo, especially where plugin boundaries or shared foundation discipline matter.

Core Features & Use Cases

  • Preserve bounded plugin ownership and enforce DevForge/shared as infrastructure-only.
  • Review cross-plugin contracts and hook boundaries to ensure release coherence and coordinated planning across the suite.
  • Provide routing guidance and boundary review follow-up for plugin-specific work and shared-foundation discipline.

Quick Start

Define and publish a ForgeWordPress suite-boundary plan detailing roles, handoffs, and escalation paths.

Frequently Asked Questions about forge-wordpress-suite-agent

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

FAQPage Schema
How do I prevent cross-plugin coupling in a WordPress monorepo?▼

Preventing cross-plugin coupling in a WordPress monorepo requires enforcing bounded plugin ownership and shared-foundation discipline. This Skill coordinates suite-level boundaries, reviewing plugin boundaries and shared infrastructure to prevent unauthorized dependencies across plugins.

What is shared-foundation discipline for WordPress plugin architecture?▼

Shared-foundation discipline for WordPress plugin architecture ensures shared layers remain infrastructure-only. It governs bounded plugin ownership by preventing shared infrastructure from containing plugin-specific logic, maintaining clear separation between individual plugins and the shared foundation.

How do I review WordPress plugin hook boundaries for release coherence?▼

Reviewing WordPress plugin hook boundaries for release coherence involves validating cross-plugin contracts and hooks. This Skill assesses hook boundaries and contracts, producing risk assessments and routing recommendations to ensure coordinated releases across the suite.

Can I use this for planning and coordinating work across bounded WordPress plugins?▼

Yes, you can use this for planning and coordinating work across bounded WordPress plugins. It applies to planning, reviewing, implementing, and coordinating monorepo work, providing routing guidance and boundary follow-up for plugin-specific tasks.

When should I not use a suite-level governance approach for WordPress plugins?▼

A suite-level governance approach for WordPress plugins is unnecessary when plugin boundaries or shared infrastructure discipline do not matter. If work is isolated within a single plugin without cross-plugin contracts or shared-foundation dependencies, standard plugin-level review suffices.