You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: create.md
+19-10Lines changed: 19 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,9 +105,16 @@ Here ROOT is the location where you found this file. For example,
105
105
- "Wrap the Slack MCP server as a reusable component"
106
106
- "Design a shared workflow for database queries"
107
107
108
-
If you need to clarify requirements or discuss options, and you are working in an interactive agent chat system, do so interactively with the user. If running non-interactively, make reasonable assumptions based on the repository context.
108
+
### Use Shared Agentic Workflows
109
+
110
+
**Load when**: User wants to learn about or use reusable workflow components, imports, orchestration, or monitoring patterns
111
+
112
+
**Use cases**:
109
113
110
-
## Reusable Components
114
+
- "What shared components are available?"
115
+
- "How do I use orchestration in my workflow?"
116
+
- "Show me monitoring patterns"
117
+
- "How do I import shared components?"
111
118
112
119
GitHub Agentic Workflows supports modular, reusable components that can be imported into your workflows. This enables:
113
120
@@ -116,7 +123,7 @@ GitHub Agentic Workflows supports modular, reusable components that can be impor
116
123
-**Separation of Concerns**: Maintain tool configs, permissions, and prompts independently
117
124
-**Consistent Patterns**: Use battle-tested components for common patterns
118
125
119
-
### Common Reusable Components
126
+
**Common Reusable Components**
120
127
121
128
**Orchestration** - Coordinate multiple workflows or agents
**Use cases**: Daily/weekly status reports, test results, analysis summaries
167
174
168
-
### Discovering Available Components
175
+
**Discovering Available Components**
169
176
170
177
Repositories using gh-aw often organize shared components in:
171
178
@@ -178,7 +185,7 @@ List available components:
178
185
ls .github/workflows/shared/
179
186
```
180
187
181
-
### Using Imports
188
+
**Using Imports**
182
189
183
190
Add imports to your workflow frontmatter:
184
191
@@ -194,7 +201,7 @@ imports:
194
201
195
202
The compiler merges imported configurations with your workflow's config. See [Packaging & Distribution](/gh-aw/guides/packaging-imports/) for complete details on import behavior and merge semantics.
196
203
197
-
### Available After Installation
204
+
**Available After Installation**
198
205
199
206
When you run `gh aw init` in a repository, several helper files become available:
200
207
@@ -211,12 +218,14 @@ When you run `gh aw init` in a repository, several helper files become available
211
218
212
219
These files are available for AI assistants to use when helping you create, update, or debug workflows. The `create.md` file (this file) references these prompts and routes you to the appropriate one based on your task.
213
220
214
-
### Learn More
221
+
**Learn More**
215
222
216
223
- **[Orchestration Guide](/gh-aw/guides/orchestration/)** - Orchestrator/worker pattern for coordinating multiple workflows
- **[Packaging & Distribution Guide](/gh-aw/guides/packaging-imports/)** - Import system, versioning, and shared components
219
226
227
+
If you need to clarify requirements or discuss options, and you are working in an interactive agent chat system, do so interactively with the user. If running non-interactively, make reasonable assumptions based on the repository context.
0 commit comments