analyze-and-plan

Analyze AEM Edge Delivery Services tasks and produce acceptance criteria drafts.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/thojava/baco --skill analyze-and-plan-thojava
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-and-plan
Source: https://github.com/thojava/baco/tree/main/.skills/analyze-and-plan
Command: npx skills add https://github.com/thojava/baco --skill analyze-and-plan-thojava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in development tasks often causes scope creep and inefficient delivery. This skill provides a structured approach to capture requirements and define acceptance criteria upfront so teams stay aligned.

Core Features & Use Cases

  • Structured requirements: systematically capture problem statements, scope, success metrics, and constraints.
  • Task coverage: applicable to new blocks, variants, modifications, bug fixes, and styling changes in AEM Edge Delivery Services.
  • Deliverables: provides a formal analysis draft you can reference during development and QA.

Quick Start

Analyze an AEM Edge Delivery task by gathering inputs, clarifying requirements, and producing a structured acceptance criteria draft.

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?

Acceptance criteria for AEM Edge Delivery Services tasks are defined by capturing problem statements, scope, success metrics, and constraints into a structured analysis draft. This ensures development teams stay aligned and prevents scope creep.

What is the best way to structure requirements analysis for AEM blocks and styling changes?

Structuring requirements analysis for AEM blocks involves systematically documenting the problem, scope, and constraints upfront. This produces a formal change documentation draft that can be integrated directly into the CDD process.

Can I use this approach for AEM bug fixes and block modifications?

Yes, this requirements analysis approach applies to AEM bug fixes, block modifications, variants, and styling changes. It streamlines project scoping by producing clear analysis and acceptance criteria across design-to-implementation workflows.

How do I prevent scope creep during AEM Edge Delivery development?

Prevent scope creep in AEM Edge Delivery development by capturing structured requirements and defining acceptance criteria upfront. This structured approach ensures teams remain aligned on task scope and constraints before implementation begins.

Does this requirements analysis workflow integrate with the CDD process?

Yes, this workflow explicitly integrates with the CDD process by producing formal analysis drafts and change documentation. These deliverables provide a clear reference during development and QA for AEM Edge Delivery Services tasks.