Repository navigation
Description
Feature Summary
Add local MCP support to block-plugin-scaffold, enabling AI clients to discover inputs, validate configuration, preview changes and generate plugins through the existing engine.
Linked Stories/Tasks
Proposed consumer: No parent or PR association proposed.
Milestones & Timeline
No dates, milestone, cycle or estimate proposed.
Proposed Solution
Design the MCP integration for use by the consuming build skill alongside the official WordPress agent skills and Figma skills. Inspect their current instructions, select applicable capabilities and document responsibilities, prerequisites, source revisions and hand-offs. Reuse upstream guidance rather than duplicating it; keep scaffold generation in the existing generator engine.
Map the current generator before designing a local adapter. See the attached research and task plan for engine issues that block a long-running MCP server (standard-output use, process.argv settings, single-request logging, process.exit, deletions beyond --force). Reuse existing validation and generation functions where safe, rather than duplicating generation logic.
The current JSON schema requires slug, name and author. Verify optional fields and supported content-model combinations against implementation. Document discovery, validation, preview and generation contracts, transport, local packaging, permissions, errors and recovery.
Separate read-only operations from generation. The current module creates a logging directory during import; generation invokes Prettier. Do not assume importing it is side-effect-free.
The consuming build skill gathers inputs and obtains the tool user’s approval. The MCP adapter validates requests and enforces safe targets; the existing generator produces the plugin files.
Support discovery, configuration validation, preview of configuration changes and plugin generation, targeting both Claude Desktop and Claude Code on macOS. Use applicable Figma skills only when a design is supplied.
Generate local files in the user-specified destination, otherwise within the designated output directory. Before generation, preview the configuration, destination, file changes, process effects and matching-file overwrites for the tool user’s approval. Approved generation overwrites matching files without stopping solely because they exist. Preserve unrelated existing files and all .git files and folders; do not delete the destination directory. The workflow ends with local files, without a repository or PR hand-off.
Reviewed community skills and local setup
Use the reviewed awesome-copilot skill sources at revision 96543145e9cb97711020b57b9d88f968062c4fc7 as conditional supporting resources, not a mandatory five-skill sequence.
codebase-memory-mcp: optional source/dependency mapping with a verified server, approved indexing and checked freshness/coverage. Confirm important scripts, configuration, documentation and tests directly; an index is not exhaustive evidence.typescript-mcp-server-generator: preferred design reference for the local adapter, subject to the target repository’s current instructions and selected SDK/transport. Reuse the existing generator and package/tooling contracts; do not initialise a parallel application or run automatic migrations.mcp-cli: discovery/schema inspection and separately authorised isolated integration checks only after verifying the actual distribution, version, configuration and permissions. Do not copy shell-interpolation examples with untrusted paths.php-mcp-server-generator: reference only, not a second implementation stack. Review the identified dependency, Composer namespace and transport-template limitations before any separately proposed use.webmcpify: reference only and excluded from the current local-server execution path. Browser WebMCP integration requires a separately requested scope and security assessment.
These community skills supplement—not replace—the applicable official WordPress and Figma skills. Preserve repository-managed skills and symlinks. If personal copies are proposed, use ~/.claude/skills/<skill-name>/, retain the reviewed revision and MIT licence/provenance, and preserve WebMCPify’s complete source directory. Saving instructions does not install servers, configure credentials or authorise their workflows. Verify supported manual-only activation controls against the installed Claude version; otherwise keep unapproved skills outside active discovery.
Before machine-dependent server startup, indexing, generation or tests, establish the OS, Claude surface/version, sanitised existing settings and managed policies; effective permissions/sandbox behaviour; MCP executable provenance, scopes and credentials mechanism; approved paths/network/data handling; and backup/rollback arrangements. Preview any configuration or installation changes separately and obtain the applicable approval. Do not adopt a universal settings JSON or infer applied protection from a proposed value.
Missing machine answers do not prevent authorised direct-source research and draft planning. Record unresolved execution prerequisites and checks not performed; do not claim installation, working connections or passing verification.
Apply these resources within this issue’s existing plugin contract: consuming skill gathers inputs/approval, adapter validates/enforces safe targets, and engine generates. Preserve approved matching-file overwrites, unrelated files and all .git files/folders; never delete the destination. Output remains local files, with no generated-deliverable repository or PR hand-off. Retain the attached plan’s separate verification requirements for Claude Desktop and Claude Code on macOS; Figma applies only when a design is supplied.
Gather machine prerequisites through a separately agreed, access-controlled response channel. This synchronised issue must not contain raw configuration, credentials, private machine paths or questionnaire answers. Resolve response handling before distribution; the issue update itself neither requests nor publishes responses.
Linked Stories/Tasks
Independent mapping and skill drafting may proceed in parallel.
Milestones & Timeline
Sequence contract mapping and adapter design before implementation and separately authorised verification. No schedule commitment established.
Acceptance Criteria
- All acceptance criteria met
- Documentation/changelog updated
- Tests added/updated
- PR uses correct branch prefix (feat/)
- Labels/types match org standards
- PR description updated with relevant details
- Changelog entry prepared for PR (if applicable)
- Labels/types match org standards
- Valid reviewed inputs produce output consistent with the existing generator.
- Invalid inputs, unsafe targets and conflicts are reported before unapproved changes.
- Discovery and validation have explicit, verified side-effect boundaries.
- Local setup, contracts, permissions, errors and recovery are documented.
- Verification records revisions, fixtures, outputs, executed checks and remaining gaps.
- Applicable official WordPress and Figma skills are identified, and their integration with the consuming build skill and local MCP generator is documented and verified, with unavailable capabilities or unperformed checks explicit.
- Responsibilities and approval hand-offs follow the division above.
- Discovery, configuration validation, configuration-change preview and generation are verified with both Claude Desktop and Claude Code on macOS.
- Figma integration is required only when a design is supplied.
- Generation requires the tool user’s approval of the preview and destination.
- Approved generation overwrites matching files while preserving unrelated files and all
.gitfiles and folders. - Output ends as local files in the selected destination.
- The adapter plan records the pinned community-skill roles and selected TypeScript/SDK/transport approach against repository instructions, preserving the existing generator and official upstream skill responsibilities.
- Each machine-dependent verification records the relevant client/version, permissions, MCP provenance and approved data/path boundaries, or explicitly identifies unresolved prerequisites and unperformed checks; no questionnaire answers or secrets are published.
Designs / References
Baseline 952f942dca8901573bc0e551c867dd1534282073: repository instructions, scripts/generate-plugin.js, .github/schemas/plugin-config.schema.json, package configuration and generation documentation. No design-file dependency assumed.
Dependencies
Verify packaging, runtime and local MCP access. Preserve existing generator/toolchain work; do not duplicate unrelated repairs. LS Skill Scaffold generates the consuming skill—it is not this WordPress generator’s MCP server.
Testing Approach
Plan isolated fixtures for valid generation, missing/invalid inputs, conflicts, unsafe paths, process failures and recovery. Compare MCP output with the underlying generator. Verify repository test commands before execution; no tests are authorised by drafting.
Additional Context
No live-site changes, releases, publishing, credential changes or unrelated generator redesign.
Definition of Ready (DoR)
- Problem statement and outcome defined
- Acceptance criteria written (Given/When/Then)
- Designs/specs/references attached (if relevant)
- Dependencies mapped
- Estimate added
- Stakeholders/approvers listed
- Milestone/iteration assigned (if applicable)
Definition of Done (DoD)
- All acceptance criteria met
- Feature implemented and tested
- Tests added/updated; CI green
-
Accessibility: WCAG 2.2 AA compliance verified (semantic HTML, keyboard support, colour contrast)Not applicable: no user interface. - Security: input validated, output escaped, no OWASP Top 10 vulnerabilities
- Performance: no measurable regression introduced
- Documentation/changelog updated if needed
- Feature toggles/rollout considered
- QA verified/UAT approved (if applicable)
-
Release notes prepared; monitoring/alerts setNot applicable: local tool, no release or hosted service. - Branch prefix is correct (feat/)
- Branch deleted after merge
- Linked issue(s) updated with latest status and closed after merge,
- The related epic should not be closed, instead updated with a comment to reflect the closed issue
Inherited gates remain unchecked pending applicability assessment; they do not authorise extra work, automatic closure or communications.
Branch instructions
Use a feat/bps-12-… branch: the organisation's branch-types.yml allows feat/, while Linear's suggested feature/… name does not match it. The integration base still needs confirming; develop exists, but its existence does not establish the approved base.
PR templates are inherited from the organisation .github repository (.github/PULL_REQUEST_TEMPLATE/). The coding-standard and linting instruction files referenced by AGENTS.md do not exist in this repository. No closing target exists until the implementing issue is created.
Expected file changes
| Operation | Path | Proposed scope |
|---|---|---|
| Conditional edit | scripts/generate-plugin.js |
Safe reuse and side-effect isolation where adapter design requires |
| Conditional edit | package.json |
Reviewed MCP entrypoint/dependencies, with corresponding verified lock changes |
| Edit | docs/GENERATE_PLUGIN.md |
Local setup, contracts, safety and CLI parity |
New module/test paths remain withheld pending placement and transport decisions. No schema change, move or deletion proposed by default.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
linear-code commentedon Nov 5, 2026
BPS-12