project-workflow-analysis-blueprint-generator

# Project Workflow Documentation Generator ## Configuration Variables ``` ${PROJECT_TYPE="Auto-detect|.NET|Java|Spring|Node.js|Python|React|Angular|Microservices|Other"} <!-- Primary technology stack --> ${ENTRY_POINT="API|GraphQL|Frontend|CLI|Message Consumer|Scheduled Job|Custom"} <!-- Starting point for the flow --> ${PERSISTENCE_TYPE="Auto-detect|SQL Database|NoSQL Database|File System|External API|Message Queue|Cache|None"} <!-- Data storage type --> ${ARCHITECTURE_PATTERN="Auto-detect|Layered|Clean|CQRS|Microservices|MVC|MVVM|Serverless|Event-Driven|Other"} <!-- Primary architecture pattern --> ${WORKFLOW_COUNT=1-5} <!-- Number of workflows to document --> ${DETAIL_LEVEL="Standard|Implementation-Ready"} <!-- Level of implementation detail to include --> ${INCLUDE_SEQUENCE_DIAGRAM=true|false} <!-- Generate sequence diagram --> ${INCLUDE_TEST_PATTERNS=true|false} <!-- Include testing approach --> ``` ## Generated Prompt ``` "Analyze the codebase and document ${WORKFLOW_COUNT} representative end-to-end workflows that can serve as implementation templates for similar features. Use the following approach: ``` ### Initial Detection Phase ``` ${PROJECT_TYPE == "Auto-detect" ? "Begin by examining the codebase structure to identify technologies: - Check for .NET solutions/projects, Spring configurations, Node.js/Express files, etc. - Identify the primary programming language(s) and frameworks in use - Determine the architectural patterns based on folder...