analyze-and-plan

Analyze AEM Edge Delivery Services requirements and define acceptance criteria.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Permit-Junction/permitjunction-website --skill analyze-and-plan-permit-junction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-and-plan
Source: https://github.com/Permit-Junction/permitjunction-website/tree/main/.claude/skills/analyze-and-plan
Command: npx skills add https://github.com/Permit-Junction/permitjunction-website --skill analyze-and-plan-permit-junction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps developers thoroughly analyze development tasks and define clear, actionable acceptance criteria before writing any code, ensuring alignment and reducing rework.

Core Features & Use Cases

  • Task Analysis: Breaks down requirements for new blocks, variants, modifications, or bug fixes.
  • Acceptance Criteria Definition: Establishes clear, testable criteria for task completion.
  • Visual Analysis Guidance: Provides a structured approach to interpreting designs and mockups.
  • Use Case: A designer provides a mockup for a new hero banner. You use this skill to analyze the visual elements, understand content requirements, and define exactly what "done" looks like, including responsive behavior and interactive states.

Quick Start

Use the analyze-and-plan skill to analyze the requirements for building a new 'testimonial-card' block.

Frequently Asked Questions about analyze-and-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define acceptance criteria for AEM Edge Delivery Services tasks?

To define acceptance criteria for AEM Edge Delivery Services tasks, analyze the specific requirements for new blocks, variants, modifications, or bug fixes, breaking them down into clear, testable conditions that establish exactly what task completion looks like.

What is the best way to analyze visual mockups for AEM development?

Analyzing visual mockups for AEM development involves interpreting the visual elements to understand content requirements, defining interactive states, and mapping out responsive behavior to ensure the resulting block matches the design intent.

How do I break down requirements for a new AEM block before coding?

Breaking down requirements for a new AEM block requires structuring the task analysis to identify content structures, variant specifications, and modification parameters, ensuring alignment and reducing rework before writing any code.

Can I use this approach for both AEM bug fixes and feature variants?

Yes, this approach supports both AEM bug fixes and feature variants by providing task-specific guidance to analyze the modification scope and establish actionable, testable acceptance criteria for each distinct scenario.

Why do I need to analyze development requirements before writing code?

Analyzing development requirements before writing code ensures thorough alignment on the task scope and visual elements, reducing rework by establishing clear, actionable acceptance criteria that define exactly what done looks like.