Extensions
Extend Plan Forge with domain-specific instructions, agents, and prompts. Share standards across teams. Install in one command. Spec Kit compatible catalog format.
pforge ext search
pforge ext info <name>
pforge ext add <name>
Catalog fetches from local extensions/catalog.json first, falls back to GitHub. Publish your own →
Row-level security policies, tenant isolation middleware, cross-tenant query prevention. Full agent for tenant isolation audits.
multi-tenancy.instructions.md
rls-patterns.instructions.md
tenant-isolation-reviewer.agent.md
pforge ext add saas-multi-tenancy
Plan Forge's L3 semantic memory layer. As of v3.6, OpenBrain is a first-class part of the framework, no extension to install. 150+ files have OpenBrain hooks, all gated behind "if configured." Pipeline prompts search memory before acting and capture decisions after.
.forge.json & the Dashboard Config tab
pforge brain hint
Bicep, Terraform, azd patterns. CAF naming conventions, security hardening, infra reviewer agent. For repos with infra/ alongside app code.
infra-reviewer.agent.md
pforge ext add azure-infrastructure
Loaded dynamically from extensions/catalog.json. Search by name, description, or tag.
Popular Spec Kit community extensions that pair well with Plan Forge's hardening pipeline. Plan Forge's catalog uses the same format — these extensions work in both tools.
Post-implementation quality gate that validates code against specification artifacts. Catches spec drift after execution.
Pairs with: Step 5 (Review Gate)
Post-implementation quality gate — reviews changes, fixes small issues (scout rule), creates tasks for medium issues, generates analysis for large issues.
Pairs with: Step 4 (Completeness Sweep)
Staff-engineer-level code review that validates implementation against spec, checks security, performance, and test coverage.
Pairs with: Reviewer agents
Reconcile implementation drift by surgically updating feature artifacts. Detects when code diverges from spec and syncs them.
Pairs with: Step 5 (Drift detection)
Post-implementation retrospective with spec adherence scoring, drift analysis, and human-gated spec updates.
Pairs with: Step 6 (Ship — postmortem)
A structured 7-step workflow for building new projects from scratch with AI assistants — from vision through implementation.
Alternative to: Plan Forge pipeline
These extensions are maintained by the Spec Kit community. Plan Forge's catalog format is compatible — install via specify extension add (Spec Kit) or pforge ext add (Plan Forge).
Package your organization's standards into a versioned, distributable extension. One extension.json manifest, any combination of instruction files, agents, and prompts.
my-extension/
├── extension.json # manifest
├── README.md # docs
├── instructions/
│ └── hipaa.instructions.md
├── agents/
│ └── hipaa-reviewer.agent.md
└── prompts/
└── hipaa-checklist.prompt.md{
"name": "healthcare-compliance",
"version": "1.0.0",
"description": "HIPAA compliance guardrails",
"author": "your-org",
"minTemplateVersion": "1.0.0",
"files": {
"instructions": ["hipaa.instructions.md"],
"agents": ["hipaa-reviewer.agent.md"],
"prompts": ["hipaa-checklist.prompt.md"]
}
}Clone or ZIP download. Version with tags. Team members install with path to the repo.
git submodule add for tight version coupling. Auto-updates with git pull.
Download and paste to .forge/extensions/. Simplest for air-gapped environments.