Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions .github/workflows/import-workflow.lock.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

29 changes: 29 additions & 0 deletions .github/workflows/import-workflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,9 @@ tools:
bash: true
edit:

engine:
model: small

timeout-minutes: 20
---

Expand Down Expand Up @@ -109,6 +112,32 @@ The workflow from the source repository may contain project-specific references.

Save the adapted workflow to `workflows/<workflow-name>.md`.

### Required delegation pattern (inlined agents)

To keep this import workflow reliable and efficient, delegate the analysis work to **inlined agents**:

1. **Summarizer agent**
Launch an inlined agent that reads the imported workflow source and returns a concise structured summary:
- workflow purpose
- trigger(s)
- required permissions
- key tools used
- safe outputs used
- expected outputs/artifacts
- custom agent references

2. **Processor agent(s)**
Launch separate inlined agent call(s) to process the imported assets independently:
- one inlined agent call to adapt the workflow content for `workflows/<workflow-name>.md`
- if custom agent files were imported, process each custom agent file in its own inlined agent call

3. **Orchestration rule**
The main agent remains the orchestrator: collect the summaries and processed outputs from inlined agents, validate consistency, and only then write files.
Consistency checks must verify that:
- permissions and safe outputs in the adapted workflow do not exceed the imported source unless explicitly required
- custom agent references in `engine.agent`/`imports` match the imported files
- documented behavior (docs + README entry) matches the adapted workflow's actual trigger/output behavior

## Step 5: Create the documentation page

Create a new file at `docs/<workflow-name>.md` following the established documentation pattern used by other docs pages in this repository. The documentation page MUST include these sections:
Expand Down