analyze-and-plan

Analyze AEM Edge Delivery Services requirements and define acceptance criteria.

Updated Mar 27, 2025

Search Tags:#planning #development #requirements #analysis #acceptance criteria #aem

Ready to run

npx skills add https://github.com/jfoxx/residentportal --skill analyze-and-plan-jfoxx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-and-plan
Source: https://github.com/jfoxx/residentportal/tree/main/.skills/analyze-and-plan
Command: npx skills add https://github.com/jfoxx/residentportal --skill analyze-and-plan-jfoxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of AEM development by ensuring clear understanding and documentation of requirements before coding begins, reducing ambiguity and rework.

Core Features & Use Cases

Requirement Analysis: Systematically breaks down development tasks (new blocks, variants, fixes) into actionable requirements.
Acceptance Criteria Definition: Establishes clear, testable criteria for task completion.
Visual Analysis: Guides users through analyzing design mockups and identifying key visual and interactive elements.
Use Case: A designer provides a mockup for a new card component. You use this skill to analyze the design, define the content authors will need to provide (image, title, description), specify styling requirements, and outline acceptance criteria for the developer.

Quick Start

Use the analyze-and-plan skill to analyze the requirements for building a new hero banner block based on the provided design mockups.

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 AEM Edge Delivery Services requirements from a design mockup?▼

To define AEM Edge Delivery Services requirements, analyze the visual mockup to identify content fields (image, title, description), specify styling needs, and document actionable functional requirements for the new block.

What is the best way to write acceptance criteria for AEM development tasks?▼

Writing acceptance criteria for AEM development involves systematically breaking down new blocks, variants, and bug fixes into clear, testable conditions that verify task completion and reduce development ambiguity.

How do I plan content authoring requirements for new AEM blocks?▼

Planning content authoring requirements for AEM blocks requires analyzing visual designs to map out the specific text, image, and structural fields content authors will need to provide.

Can I use this approach to analyze AEM variants and bug fixes?▼

Yes, this approach analyzes AEM variants and bug fixes by systematically evaluating functional needs and establishing clear, testable acceptance criteria for each specific modification task.

Why do I need to analyze requirements before coding AEM Edge Delivery Services?▼

Analyzing requirements before coding AEM Edge Delivery Services ensures clear understanding and documentation of task needs, which reduces ambiguity and prevents rework during the content-driven development workflow.