Athenian Plug-in Forge for WordPress
product details.
Athenian Plug-in Forge for WordPress creates a WordPress-native planning workspace for plugin requests, readiness scoring, implementation briefs, and downloadable plugin artifacts. It helps teams move plugin concepts from vague requests into defined scope, build records, and delivery packages while keeping data, permissions, and automation aligned with the broader Athenian Platform Ecosystem.
Athenian Plug-in Forge is an AI-assisted WordPress and WooCommerce plugin planning, scaffolding, packaging, and delivery workspace. It is designed to turn loose plugin requests into structured implementation handoffs before code generation begins, helping teams clarify the business goal, required surfaces, WooCommerce touchpoints, integrations, permissions, QA expectations, and delivery requirements.
Instead of generating code from a single vague prompt, Plug-in Forge creates a readiness-scored build record with open questions, implementation recommendations, a proposed file tree, pipeline states, timeline logs, generated scaffold files, and downloadable ZIP artifacts. It supports both admin-side planning and customer-facing plugin request workflows, making it useful for Athenian implementation teams, agencies, developers, and technical clients who need a more repeatable way to scope and package plugin ideas.
The current implementation is intentionally staged as a practical planning and mock-generation environment. It uses a local mock AI planner and generator to validate the workflow, generate lightweight scaffold files, and package ZIPs, while leaving a clear future path to connect the planning and generation layer to Athenian Platform Core AI services or another production model provider.
For the broader Athenian Platform, Plug-in Forge is best positioned as a developer operations and delivery tool: a structured intake, readiness review, build manifest, scaffold generator, ZIP packager, and project handoff system for WordPress and WooCommerce plugin development.
How Athenian Plug-in Forge for WordPress fits the Athenian Platform
Platform role: Athenian Plug-in Forge for WordPress is part of the platform foundation layer. Its Developer Tooling responsibilities help establish shared conventions that other Athenian modules can use without duplicating lower-level infrastructure.
Connected scope: Athenian Plug-in Forge for WordPress is designed to work inside a WordPress and WooCommerce operating environment where storefront, customer, order, identity, payment, fulfillment, automation, and reporting context can remain connected across relevant modules instead of being trapped in isolated add-ons.
From module to operating platform: Athenian Brands organizes the ecosystem in four connected layers: Platform Kernel and Platform Core foundations; focused capability plugins; implementation and integration services; and operating brands such as PrintGhost.ai, Athenian Marketplace, Athenian Academy, and Athenian Unÿa that apply the same patterns to real business workflows.
Plugin Planning
Turn Vague Plugin Requests Into Structured Implementation Briefs
Athenian Plug-in Forge slows generation down at the right moment by asking
for the missing business logic, WordPress surfaces, WooCommerce touchpoints,
integrations, permissions, QA rules, and delivery requirements before a
scaffold is packaged.
| Planning Layer | Operational Value |
|---|---|
| Guided Intake | Capture the plugin request, business problem, intended user, expected outcome, touchpoints, rules, integrations, and delivery notes. |
| Planning Modes | Support guided forge mode for stricter readiness review and rapid draft mode for faster assumption-based scaffolding. |
| Surface Selection | Account for admin dashboards, storefront shortcodes, WooCommerce flows, external services, reporting, and automation requirements. |
| Readiness Lights | Score request clarity, touchpoints, rules, integrations, and delivery readiness with green, yellow, and red planning states. |
- Generates open questions, recommendations, requirements, feedback notes, and pipeline states.
- Helps operators identify missing implementation details before scaffold generation begins.
- Supports admin-side and customer-facing planning workflows.
- Uses the customer-facing planning studio shortcode name
'pif'.
Build Packaging
Create Tracked Build Records, Scaffold Files, and Downloadable Plugin ZIPs
Plug-in Forge stores each request as a file-backed build with a manifest,
timeline logs, generated scaffold files, review state, and a ZIP package
that can be marked as draft or ready depending on planning completeness.
Track build ID, owner, mode, phase, percent complete, questions, requirements, and readiness state
Generate starter plugin files based on selected surfaces and requested functionality
Package generated files into nonce-protected downloadable plugin ZIPs
| Build Layer | How It Helps |
|---|---|
| Manifest Storage | Stores build metadata, prompt, owner, plugin details, structure, files, review state, artifacts, and status in manifest.json. |
| File-Backed Builds | Writes build state under wp-content/uploads/pif/builds/<build_id>/ without requiring a custom database table. |
| Generated Structure | Creates starter files such as plugin bootstrap, core class, utility class, admin controller, shortcode controller, WooCommerce stub, assets, README, and manifest. |
| Draft vs. Ready | Can package incomplete builds as draft ZIPs while reserving ready status for builds with fully resolved planning lights. |
- Packages generated files with PHP
ZipArchive. - Stores completed ZIP output as
output.zipinside the build directory. - Protects downloads through owner checks and nonce-protected AJAX download actions.
- Uses workflow actions such as
pif_plan_workflow,pif_list_builds,pif_generate_build, andpif_download_build.
Developer Operations
Support Admin, Customer, and Developer Plugin-Build Workflows
Athenian Plug-in Forge provides a WordPress admin dashboard, a customer-facing
planning studio, owner-aware build access, WP-CLI commands, protocol parsing,
and a mock AI layer that can be replaced with production AI services later.
| Workflow Surface | Operational Purpose |
|---|---|
| Admin Dashboard | Adds a top-level Plug-in Forge admin page where operators can plan, review, generate, package, and download builds. |
| Customer Studio | Allows signed-in users or guest browser sessions to submit plugin ideas, review readiness questions, and access their own build desk. |
| WP-CLI Workflow | Supports developer commands for planning, generating, zipping, checking status, listing builds, deleting builds, and testing protocol parsing. |
| AI Upgrade Path | Uses a local mock planner/generator today while preserving a workflow contract suitable for Athenian Platform Core AI or another provider later. |
Planning before generation:
Plug-in Forge is strongest as a structured intake and delivery workspace,
helping teams define what should be built, what details are missing, and
how the first scaffold should be packaged before deeper development begins.
- Registers the admin page under Plug-in Forge with the
manage_optionscapability. - Tracks build ownership for admins, logged-in users, and guest sessions through a
pif_client_tokencookie. - Includes WP-CLI commands such as
wp pif plan,wp pif generate,wp pif zip,wp pif status,wp pif list, andwp pif delete. - Builds toward production AI generation, streamed protocol events, PHP syntax checks, security scans, WordPress coding-standard review, build retention controls, customer notifications, and Athenian Platform Core integration.