project-workflow-analysis-blueprint-generator

Name: project-workflow-analysis-blueprint-generator
Author: github

9.2kinstalls4.6kforks

How to install project-workflow-analysis-blueprint-generator?

github/awesome-copilot/project-workflow-analysis-blueprint-generator

$npx -y skills add github/awesome-copilot --skill project-workflow-analysis-blueprint-generator

Installs into the current project.

Summary

Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers

Files · 1

View on GitHub

SKILL.md

1	# Project Workflow Documentation Generator
2
3	## Configuration Variables
4
5	```
6	${PROJECT_TYPE="Auto-detect\|.NET\|Java\|Spring\|Node.js\|Python\|React\|Angular\|Microservices\|Other"}
7	<!-- Primary technology stack -->
8
9	${ENTRY_POINT="API\|GraphQL\|Frontend\|CLI\|Message Consumer\|Scheduled Job\|Custom"}
10	<!-- Starting point for the flow -->
11
12	${PERSISTENCE_TYPE="Auto-detect\|SQL Database\|NoSQL Database\|File System\|External API\|Message Queue\|Cache\|None"}
13	<!-- Data storage type -->
14
15	${ARCHITECTURE_PATTERN="Auto-detect\|Layered\|Clean\|CQRS\|Microservices\|MVC\|MVVM\|Serverless\|Event-Driven\|Other"}
16	<!-- Primary architecture pattern -->
17
18	${WORKFLOW_COUNT=1-5}
19	<!-- Number of workflows to document -->
20
21	${DETAIL_LEVEL="Standard\|Implementation-Ready"}
22	<!-- Level of implementation detail to include -->
23
24	${INCLUDE_SEQUENCE_DIAGRAM=true\|false}
25	<!-- Generate sequence diagram -->
26
27	${INCLUDE_TEST_PATTERNS=true\|false}
28	<!-- Include testing approach -->
29	```
30
31	## Generated Prompt
32
33	```
34	"Analyze the codebase and document ${WORKFLOW_COUNT} representative end-to-end workflows
35	that can serve as implementation templates for similar features. Use the following approach:
36	```
37
38	### Initial Detection Phase
39
40	```
41	${PROJECT_TYPE == "Auto-detect" ?
42	"Begin by examining the codebase structure to identify technologies:
43	- Check for .NET solutions/projects, Spring configurations, Node.js/Express files, etc.
44	- Identify the primary programming language(s) and frameworks in use
45	- Determine the architectural patterns based on folder structure and key components"
46	: "Focus on ${PROJECT_TYPE} patterns and conventions"}
47	```
48
49	```
50	${ENTRY_POINT == "Auto-detect" ?
51	"Identify typical entry points by looking for:
52	- API controllers or route definitions
53	- GraphQL resolvers
54	- UI components that initiate network requests
55	- Message handlers or event subscribers
56	- Scheduled job definitions"
57	: "Focus on ${ENTRY_POINT} entry points"}
58	```
59
60	```
61	${PERSISTENCE_TYPE == "Auto-detect" ?
62	"Determine persistence mechanisms by examining:
63	- Database context/connection configurations
64	- Repository implementations
65	- ORM mappings
66	- External API clients
67	- File system interactions"
68	: "Focus on ${PERSISTENCE_TYPE} interactions"}
69	```
70
71	### Workflow Documentation Instructions
72
73	For each of the `${WORKFLOW_COUNT}` most representative workflow(s) in the system:
74
75	#### 1. Workflow Overview
76	- Provide a name and brief description of the workflow
77	- Explain the business purpose it serves
78	- Identify the triggering action or event
79	- List all files/classes involved in the complete workflow
80
81	#### 2. Entry Point Implementation
82
83	API Entry Points:
84	```
85	${ENTRY_POINT == "API" \|\| ENTRY_POINT == "Auto-detect" ?
86	"- Document the API controller class and method that receives the request
87	- Show the complete method signature including attributes/annotations
88	- Include the full request DTO/model class definition
89	- Document validation attributes and custom validators
90	- Show authentication/authorization attributes and checks" : ""}
91	```
92
93	GraphQL Entry Points:
94	```
95	${ENTRY_POINT == "GraphQL" \|\| ENTRY_POINT == "Auto-detect" ?
96	"- Document the GraphQL resolver class and method
97	- Show the complete schema definition for the query/mutation
98	- Include input type definitions
99	- Show resolver method implementation with parameter handling" : ""}
100	```
101
102	Frontend Entry Points:
103	```
104	${ENTRY_POINT == "Frontend" \|\| ENTRY_POINT == "Auto-detect" ?
105	"- Document the component that initiates the API call
106	- Show the event handler that triggers the request
107	- Include the API client service method
108	- Show state management code related to the request" : ""}
109	```
110
111	Message Consumer Entry Points:
112	```
113	${ENTRY_POINT == "Message Consumer" \|\| ENTRY_POINT == "Auto-detect" ?
114	"- Document the message handler class and method
115	- Show message subscription configuration
116	- Include the complete message model definition
117	- Show deserialization and validation logic" : ""}
118	```
119
120	#### 3. Service Layer Implementation
121	- Document each service class involved with their dependencies
122	- Show the complete method signatures with parameters and return types
123	- Include actual method implementations with key business logic
124	- Document interface definitions where applicable
125	- Show dependency injection registration patterns
126
127	CQRS Patterns:
128	```
129	${ARCHITECTURE_PATTERN == "CQRS" \|\| ARCHITECTURE_PATTERN == "Auto-detect" ?
130	"- Include complete command/query handler impl

People who liked this also viewed

6 picks

Type

project-workflow-analysis-blueprint-generator

9.2kinstalls4.6kforks

View on GitHub

How to install project-workflow-analysis-blueprint-generator?

github/awesome-copilot/project-workflow-analysis-blueprint-generator

$npx -y skills add github/awesome-copilot --skill project-workflow-analysis-blueprint-generator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Project Workflow Documentation Generator
2
3	## Configuration Variables
4
5	```
6	${PROJECT_TYPE="Auto-detect\|.NET\|Java\|Spring\|Node.js\|Python\|React\|Angular\|Microservices\|Other"}
7	<!-- Primary technology stack -->
8
9	${ENTRY_POINT="API\|GraphQL\|Frontend\|CLI\|Message Consumer\|Scheduled Job\|Custom"}
10	<!-- Starting point for the flow -->
11
12	${PERSISTENCE_TYPE="Auto-detect\|SQL Database\|NoSQL Database\|File System\|External API\|Message Queue\|Cache\|None"}
13	<!-- Data storage type -->
14
15	${ARCHITECTURE_PATTERN="Auto-detect\|Layered\|Clean\|CQRS\|Microservices\|MVC\|MVVM\|Serverless\|Event-Driven\|Other"}
16	<!-- Primary architecture pattern -->
17
18	${WORKFLOW_COUNT=1-5}
19	<!-- Number of workflows to document -->
20
21	${DETAIL_LEVEL="Standard\|Implementation-Ready"}
22	<!-- Level of implementation detail to include -->
23
24	${INCLUDE_SEQUENCE_DIAGRAM=true\|false}
25	<!-- Generate sequence diagram -->
26
27	${INCLUDE_TEST_PATTERNS=true\|false}
28	<!-- Include testing approach -->
29	```
30
31	## Generated Prompt
32
33	```
34	"Analyze the codebase and document ${WORKFLOW_COUNT} representative end-to-end workflows
35	that can serve as implementation templates for similar features. Use the following approach:
36	```
37
38	### Initial Detection Phase
39
40	```
41	${PROJECT_TYPE == "Auto-detect" ?
42	"Begin by examining the codebase structure to identify technologies:
43	- Check for .NET solutions/projects, Spring configurations, Node.js/Express files, etc.
44	- Identify the primary programming language(s) and frameworks in use
45	- Determine the architectural patterns based on folder structure and key components"
46	: "Focus on ${PROJECT_TYPE} patterns and conventions"}
47	```
48
49	```
50	${ENTRY_POINT == "Auto-detect" ?
51	"Identify typical entry points by looking for:
52	- API controllers or route definitions
53	- GraphQL resolvers
54	- UI components that initiate network requests
55	- Message handlers or event subscribers
56	- Scheduled job definitions"
57	: "Focus on ${ENTRY_POINT} entry points"}
58	```
59
60	```
61	${PERSISTENCE_TYPE == "Auto-detect" ?
62	"Determine persistence mechanisms by examining:
63	- Database context/connection configurations
64	- Repository implementations
65	- ORM mappings
66	- External API clients
67	- File system interactions"
68	: "Focus on ${PERSISTENCE_TYPE} interactions"}
69	```
70
71	### Workflow Documentation Instructions
72
73	For each of the `${WORKFLOW_COUNT}` most representative workflow(s) in the system:
74
75	#### 1. Workflow Overview
76	- Provide a name and brief description of the workflow
77	- Explain the business purpose it serves
78	- Identify the triggering action or event
79	- List all files/classes involved in the complete workflow
80
81	#### 2. Entry Point Implementation
82
83	API Entry Points:
84	```
85	${ENTRY_POINT == "API" \|\| ENTRY_POINT == "Auto-detect" ?
86	"- Document the API controller class and method that receives the request
87	- Show the complete method signature including attributes/annotations
88	- Include the full request DTO/model class definition
89	- Document validation attributes and custom validators
90	- Show authentication/authorization attributes and checks" : ""}
91	```
92
93	GraphQL Entry Points:
94	```
95	${ENTRY_POINT == "GraphQL" \|\| ENTRY_POINT == "Auto-detect" ?
96	"- Document the GraphQL resolver class and method
97	- Show the complete schema definition for the query/mutation
98	- Include input type definitions
99	- Show resolver method implementation with parameter handling" : ""}
100	```
101
102	Frontend Entry Points:
103	```
104	${ENTRY_POINT == "Frontend" \|\| ENTRY_POINT == "Auto-detect" ?
105	"- Document the component that initiates the API call
106	- Show the event handler that triggers the request
107	- Include the API client service method
108	- Show state management code related to the request" : ""}
109	```
110
111	Message Consumer Entry Points:
112	```
113	${ENTRY_POINT == "Message Consumer" \|\| ENTRY_POINT == "Auto-detect" ?
114	"- Document the message handler class and method
115	- Show message subscription configuration
116	- Include the complete message model definition
117	- Show deserialization and validation logic" : ""}
118	```
119
120	#### 3. Service Layer Implementation
121	- Document each service class involved with their dependencies
122	- Show the complete method signatures with parameters and return types
123	- Include actual method implementations with key business logic
124	- Document interface definitions where applicable
125	- Show dependency injection registration patterns
126
127	CQRS Patterns:
128	```
129	${ARCHITECTURE_PATTERN == "CQRS" \|\| ARCHITECTURE_PATTERN == "Auto-detect" ?
130	"- Include complete command/query handler impl

People who liked this also viewed

6 picks

Type