Use when a WordPress feature, plugin, or subsystem needs a formal architecture description before implementation. Produces architecture views, architectural decisions (with rationale), constraints, risks, and requirement-linked coverage references to SRS IDs, with SyRS enrichment when available. Aligns architecture…
Use when generating or reviewing PHP, JavaScript, CSS, or HTML code in any WordPress context (plugins, themes, block themes, mu-plugins, Gutenberg blocks) to enforce WordPress Coding Standards (WPCS). Covers naming conventions, formatting, sanitization/escaping patterns, SQL safety, and tooling setup.
Use when completed WordPress software needs developer-facing API, integration, and extension documentation. Produces class references, API guides, integration instructions, code examples, and troubleshooting for developers and integrators. Aligns to ISO/IEC/IEEE 26514:2022 (Information for Use — Developer Reference).…
Use when reviewing WordPress plugins for WordPress.org directory submission readiness, including plugin-check blocking items, disclosure/readme requirements, licensing, and submission-specific security/compliance rules.
Use when completed WordPress software needs public-facing, publication-ready documentation. Transforms upstream artifacts (SRS, architecture, developer docs, user docs) into audience-appropriate content suitable for any output format (website, PDF, help center, printed). Aligns to ISO/IEC/IEEE 26514:2022 (Information…
Use when WordPress software needs procedural testing framework and verification approach. Produces test strategy, test plans, test procedures, and test case specifications for developers and QA teams. Aligns to ISO/IEC/IEEE 29119-2:2021 (Test Process) with ISO/IEC TR 29119-6:2021 (Agile Tailoring). Use during…
Use when a WordPress feature, plugin, or block needs a formal pre-implementation specification package. Uses SRS as the default downstream handoff artifact and adds BRS, StRS, OpsCon, and SyRS only when stronger business, stakeholder, operational, or system traceability is needed. Aligns requirements work to…
Use when you need a comprehensive inventory of an unknown or existing WordPress site: content statistics, custom post types, ACF field groups, custom blocks, theme architecture, plugins, global features, and migration considerations. Generates a structured markdown report for AI analysis.
Use when WordPress software is ready for stakeholder validation before release or handoff. Produces stakeholder-friendly acceptance criteria, test scenarios, execution evidence, and a release decision summary. Uses SRS as the canonical upstream handoff artifact, with StRS and OpsCon enriching business-fit coverage…
Use when completed WordPress software needs end-user, operator, or administrator documentation. Produces task-based guides, workflows, procedures, FAQs, and troubleshooting for non-technical stakeholders. Aligns to ISO/IEC/IEEE 26514:2022 (Information for Use — Task-based). Use after wp-block-development…
★not rated 2 2mo agoA83 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: