// Analyze WordPress block theme projects for FRD generation. Provides block/pattern inventory analysis, theme.json specifications, plugin justification framework, Core Web Vitals performance budget, and WordPress-specific estimation patterns.
Generate properly formatted Teamwork CSV files from Functional Requirements Documents. Converts FRD requirements into CSV backlog with task hierarchy, priorities, story points, and estimated hours. Automatically populates estimated time from story point conversion. Invoke when user asks to "export to CSV", "create Teamwork backlog", or needs project backlog file.
Generate comprehensive FRD markdown structure with all required sections. Provides section templates, numbering conventions (FR-XXX, TR-XXX, US-XXX), platform-specific additions, and output format guidelines. Invoke when requirements are gathered and ready to structure into FRD document.
Provide story point estimation guidance with hour calculations for software development tasks. Uses Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34+) and converts story points to hours. Includes platform-specific adjustments and velocity calculations.
| name | wordpress-analyzer |
| description | Analyze WordPress block theme projects for FRD generation. Provides block/pattern inventory analysis, theme.json specifications, plugin justification framework, Core Web Vitals performance budget, and WordPress-specific estimation patterns. |
Analyze WordPress block theme projects to generate comprehensive technical requirements, block/pattern inventories, and performance budgets for FRDs.
WordPress block theme development in 2026 requires strategic decisions about blocks vs patterns vs custom development, aggressive performance optimization for Core Web Vitals, and careful plugin selection to avoid performance degradation.
Activate this skill when:
Use this decision tree for every UI component:
UI Component Requirement
↓
Can core blocks achieve this? (Cover, Group, Columns, Query Loop, etc.)
YES → Use core blocks
NO ↓
Can core blocks be composed into a pattern?
YES → Create pattern (2-8 hours)
NO ↓
Do you have ACF PRO? Are fields simple?
YES → Use ACF block (4-20 hours)
NO ↓
Is complex interactivity or state management required?
YES → Build custom Gutenberg block (12-120 hours)
NO → Reconsider: probably should be pattern
Decision Criteria:
Use Core Blocks When:
Use Patterns When:
Use ACF Blocks When:
Build Custom Gutenberg Blocks When:
For every plugin, document:
1. Purpose: What specific need does this plugin solve? 2. Alternatives: Could this be achieved without a plugin? 3. Performance Impact: Lighthouse score before/after, added KB 4. Maintenance Risk: Last update, active installs, support quality 5. Cost: One-time, annual, or monthly 6. Justification: Why is this plugin worth the trade-offs?
Red Flags (Consider Alternatives):
Plugin Budget:
Mandatory Targets (Google Search Ranking Factor):
Asset Budget:
Performance Optimization Strategies:
Performance Enforcement:
Required theme.json Sections:
1. Version (use v3 for WordPress 6.8+)
{
"version": 3
}
2. Settings
3. Styles
4. Template Parts
5. Custom Templates
Story Point Estimates for theme.json Work:
When analyzing a WordPress project for FRD generation:
For each UI component identified in discovery:
| Component | Core Blocks | Pattern | ACF | Custom | Justification | Points |
|-----------|-------------|---------|-----|--------|---------------|--------|
| Hero | ✓ | ✓ | - | - | Core sufficient | 2 |
| Products | Query Loop | ✓ | - | - | Core + CPT | 3 |
| Team | - | - | ✓ | - | Repeating fields| 5 |
| Pricing | - | - | - | ✓ | Interactivity | 13 |
List proposed plugins with justifications:
**Performance Plugins:**
- WP Rocket ($59/year) - Page cache, critical CSS, lazy load - Justified by LCP target
- Imagify ($10/month) - WebP conversion, compression - Justified by image-heavy site
**SEO Plugins:**
- Yoast SEO (Free) - Meta tags, schema markup - Justified by SEO requirements
**Form Plugins:**
- Gravity Forms ($59/year) - Complex multi-step form - Justified by form complexity
**Total: 4 plugins, $128/year + $120/year**
**Core Web Vitals Targets:**
- LCP: < 2.5s (3G), < 1.5s (4G)
- INP: < 200ms
- CLS: < 0.1
**Asset Budget:**
- JS: 280KB (current) → < 300KB (target)
- CSS: 85KB (current) → < 100KB (target)
- Images: WebP, < 200KB each, lazy loaded
**Story Points for Optimization:**
- Initial optimization: 5 points (20 hours)
- Ongoing monitoring: 2 points/sprint (8 hours)
**theme.json Requirements:**
- Color palette: 6 colors (primary, secondary, accent, 3 grays)
- Typography: 2 fonts (heading, body), 5 sizes (12px-48px)
- Spacing: 8 presets (0.25rem-4rem)
- Layout: contentSize 720px, wideSize 1200px
**Story Points:** 5 points (12-16 hours)
**WordPress-Specific Risks:**
1. **Performance Degradation Risk**
- Likelihood: High
- Mitigation: Performance budget, Lighthouse audits
- Contingency: +5-8 points
2. **Custom Block Scope Creep**
- Likelihood: Medium-High
- Mitigation: Pattern-first framework
- Prevention: "Could this be a pattern?" code review
3. **Editor Training Gap**
- Likelihood: Medium
- Mitigation: Pattern library, video training
- Contingency: +2-3 points
When providing WordPress analysis for FRDs, structure output as:
## WordPress Block Theme Analysis
### Block/Pattern Inventory
[Table with component decisions]
### theme.json Configuration
[Detailed specifications]
### Plugin Ecosystem
[Justified plugin list with costs]
### Performance Budget
[Core Web Vitals targets and enforcement]
### Risk Assessment
[WordPress-specific risks and mitigation]
### Success Criteria
[Technical and functional gates]
templates/block-inventory-template.md - Standard block analysis matrixtemplates/themejson-spec.md - Complete theme.json specification guidetemplates/plugin-justification.md - Plugin decision frameworktemplates/performance-budget.md - Core Web Vitals targets and enforcementSkill Version: 1.0.0 (Phase 2 v0.3.0) Last Updated: 2026-03-16 Platform: WordPress 6.8+, PHP 8.1+