analyze-and-plan

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

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill analyze-and-plan-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-and-plan
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/analyze-and-plan
Command: npx skills add https://github.com/valithedge/etisalatedge --skill analyze-and-plan-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes development requirements and generates structured acceptance criteria for AEM Edge Delivery Services (EDS) tasks. Use when the user needs to define acceptance criteria, write requirements, scope work, or create a definition of done for EDS blocks, components, variants, bug fixes, or styling changes. Produces task breakdowns, identifies edge cases, and documents analysis for new blocks, variants, behavior modifications, CSS-only changes, and bug fixes.

Core Features & Use Cases

  • Produces task breakdowns and structured acceptance criteria for EDS work items.
  • Identifies edge cases and documents analysis for blocks, variants, behavior changes, or CSS-only updates.
  • Suitable for defining acceptance criteria, scoping work, or creating a definition of done for EDS-related tasks.

Quick Start

Provide structured acceptance criteria for the given EDS task requirements.

Frequently Asked Questions about analyze-and-plan

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

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

You generate structured acceptance criteria for AEM Edge Delivery Services by analyzing development requirements, producing task breakdowns, identifying edge cases, and documenting analysis for blocks, variants, or bug fixes.

What is the best way to scope work and define done for EDS components?

Scoping work and defining done for EDS components is achieved by analyzing requirements to produce task breakdowns and structured acceptance criteria tailored for blocks, behavior modifications, CSS-only changes, and bug fixes.

How do I identify edge cases when planning EDS styling changes?

Edge cases for EDS styling changes are identified through requirement analysis that documents behavior modifications and CSS-only updates, ensuring comprehensive task breakdowns and structured acceptance criteria for variants and bug fixes.

Can I use requirement analysis to create task breakdowns for EDS bug fixes?

Requirement analysis can be used to create task breakdowns for EDS bug fixes by evaluating the requirements and generating structured acceptance criteria that document analysis and identify edge cases for bug fixes and behavior modifications.

When do I need to document analysis for EDS block variants?

Documenting analysis for EDS block variants is needed when defining acceptance criteria, writing requirements, scoping work, or creating a definition of done for new blocks, variants, behavior modifications, CSS-only changes, and bug fixes.