AlexandrAI AGENTS.md
agents-md

testPlan PPT Agent Team Guide

Project-specific AGENTS.md guidance for the testPlan PPT multi-agent workflow, PPT analyzer, test plan writer, slide composer, structured PPT visuals, and output folders.

AGENTS.md

Guidance for coding agents working on the testPlan PPT agent workflow.

Project Overview

testPlan is a Claude agent workflow for analyzing reference PPT/PPTX files, generating structured test plan content, and composing slide-by-slide markdown for PowerPoint creation. The workflow separates PPT structure extraction, test plan writing, slide formatting, and orchestrator skills.

Project Map

  • .claude/agents/ppt-analyzer.md extracts reference deck structure into _workspace/01_ppt_analysis.md.
  • .claude/agents/test-plan-writer.md owns structured test plan content.
  • .claude/agents/slide-composer.md formats copy-paste-ready slide markdown.
  • .claude/skills/ppt-analysis/skill.md supports PPT/PPTX analysis.
  • .claude/skills/test-plan-generation/skill.md supports test plan generation.
  • .claude/skills/slide-formatting/skill.md supports slide composition.
  • .claude/skills/test-plan-orchestrator/skill.md coordinates the workflow.
  • output/ contains generated slide-section markdown decks.

Setup Commands

bashfind .claude -type f -name '*.md' -print
find output -maxdepth 2 -type f -name '*.md' -print

Change Rules For Agents

  • Preserve the analyzer -> writer -> composer workflow order.
  • Keep PPT analysis output in _workspace/01_ppt_analysis.md.
  • Keep generated slide content under output//.
  • Use structured PPT Visual blocks for diagrams instead of ASCII art.
  • Keep slide density rules explicit so downstream PowerPoint generation does not overflow.
  • Preserve bilingual slide labeling when required by the workflow.
  • Do not embed private client data in public examples.

Verification

bashfind .claude/agents .claude/skills -type f -name '*.md' -print

Review generated slide markdown for structured visual blocks, slide density, and copy-paste readiness.

Security Notes

Reference decks may contain client information. Do not publish deck contents, private names, or source file paths. Use generic examples in public docs.

PR Checklist

  • Agent roles remain separated.
  • Output paths stay predictable.
  • Slide visual specs avoid ASCII diagrams.
  • Generated deck sections follow density rules.