skills.rest
adobe-summit2026-l613
adobe-summit2026-l613OFFICIAL
Explore all skills by this author →
GitHub

analyze-and-plan

Analyze AEM development requirements and define acceptance criteria before coding.

Updated Mar 12, 2026
Search Tags:#development#requirements#plan#aem#analyze#acceptance-criteria
One-click install
npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill analyze-and-plan-adobe-summit2026-l613
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-and-plan
Source: https://github.com/adobe-summit2026-l613/las-vegas-events/tree/main/.skills/analyze-and-plan
Command: npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill analyze-and-plan-adobe-summit2026-l613

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This analysis skill helps teams clarify requirements and acceptance criteria before coding, reducing rework and miscommunication.

Core Features & Use Cases

  • Structured steps: visual analysis (when visuals are provided), requirements capture, acceptance criteria definition, and documentation artifacts.
  • Task applicability: suitable for planning new blocks, variants, modifications, bug fixes, and styling changes in AEM Edge Delivery projects.
  • Documentation focus: produces working artifacts and clear guidance to align teams.

Quick Start

Define the task, gather inputs, and follow a guided analysis to produce a clear acceptance criteria set.

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 development tasks before coding?▼

Defining acceptance criteria for AEM tasks requires a structured analysis process covering visual review, requirements capture, and documentation. This approach ensures teams align on expectations before coding begins.

What is the best way to plan requirements for new blocks and variants in AEM Edge Delivery?▼

Planning requirements for AEM Edge Delivery blocks involves guided steps to analyze visuals, capture requirements, and define acceptance criteria. This produces clear documentation artifacts that guide subsequent development.

Can I use structured requirement analysis for bug fixes and styling changes in AEM projects?▼

Yes, structured requirement analysis applies to bug fixes and styling changes in AEM projects. It guides you through visual analysis and acceptance criteria definition to reduce rework and miscommunication across all modification types.

How do I reduce miscommunication when planning modifications for AEM development?▼

You can reduce miscommunication during AEM modification planning by generating working artifacts that document visual analysis, requirements, and acceptance criteria. This structured documentation aligns team members before implementation starts.

Do I need visual inputs to analyze development requirements and define acceptance criteria?▼

Visual inputs are used for analysis when provided, but the requirement and acceptance criteria definition steps still proceed without them. The structured process adapts to available inputs to produce clear development guidance.

Related Skills

Explore More Software Engineering Skills→
openaiopenai
488

gather-business-context

Gather business context from connected sources to frame analytical tasks.

Official
Advanced
valithedgevalithedge

analyze-and-plan

Analyze development requirements and generate structured acceptance criteria for AEM Edge Delivery Services tasks.

Community
Intermediate
juricamigac-from-hrjuricamigac-from-hr

analyze-and-plan

Analyze development requirements and define acceptance criteria for AEM Edge Delivery Services tasks.

Official
Intermediate
mhaackmhaack

analyze-and-plan

Analyze development requirements and define acceptance criteria for AEM Edge Delivery Services tasks.

Community
Advanced