Open
Conversation
…dation and testing Tested all code snippets with this power and fixed all discovered issues Reviewed POWER.md and updated it
bfreiberg
reviewed
Apr 1, 2026
| displayName: "AWS Step Functions" | ||
| description: "Build AWS Step Functions state machines using the JSONata query language. Covers Amazon States Language (ASL) structure, all state types, variables, data transformation, error handling, and service integrations." | ||
| keywords: ["step functions", "state machine", "serverless", "jsonata", "asl", "amazon states language", "workflow orchestration"] | ||
| author: "[Jeff Palmer](https://linkedin.com/in/jeffrey-palmer/)" |
There was a problem hiding this comment.
Suggested change
| author: "[Jeff Palmer](https://linkedin.com/in/jeffrey-palmer/)" | |
| author: "AWS" |
| name: "aws-step-functions" | ||
| displayName: "AWS Step Functions" | ||
| description: "Build AWS Step Functions state machines using the JSONata query language. Covers Amazon States Language (ASL) structure, all state types, variables, data transformation, error handling, and service integrations." | ||
| keywords: ["step functions", "state machine", "serverless", "jsonata", "asl", "amazon states language", "workflow orchestration"] |
There was a problem hiding this comment.
Suggested change
| keywords: ["step functions", "state machine", "serverless", "jsonata", "asl", "amazon states language", "workflow orchestration"] | |
| keywords: ["step functions", "state machine", "serverless", "jsonata", "asl", "amazon states language", "workflow", "orchestration"] |
| --- | ||
| name: "aws-step-functions" | ||
| displayName: "AWS Step Functions" | ||
| description: "Build AWS Step Functions state machines using the JSONata query language. Covers Amazon States Language (ASL) structure, all state types, variables, data transformation, error handling, and service integrations." |
There was a problem hiding this comment.
Suggested change
| description: "Build AWS Step Functions state machines using the JSONata query language. Covers Amazon States Language (ASL) structure, all state types, variables, data transformation, error handling, and service integrations." | |
| description: "Build workflows with AWS Step Functions state machines using the JSONata query language. Covers Amazon States Language (ASL) structure, all state types, variables, data transformation, error handling, and service integrations." |
|
|
||
| # AWS Step Functions | ||
|
|
||
| AWS Step Functions provides visual workflow orchestration with native integrations to 9,000+ API actions across 200+ AWS services. Define workflows as state machines in Amazon States Language using the JSONata query language instead of legacy JSONPath. |
There was a problem hiding this comment.
This mixes description (what is SFN) with guidance (Not using JSONPath), separate the two parts.
| | `Pass` | Pass input to output, optionally injecting or transforming data | | ||
| | `Succeed` / `Fail` | End execution successfully or with an error and cause | | ||
|
|
||
| ### Setting the State Machine Query Language |
There was a problem hiding this comment.
Extract all the JSONata specific parts to a separate file (or distribute it across the existing files) to keep the POWER.md as concise as possible. The guidance is around 100 lines if I recall correctly
There was a problem hiding this comment.
Doc is too long, consider removing some of the examples or only highlighting the key parts.
|
|
||
| **Merging result into input** (`ResultPath: "$.field"`): | ||
| ```json | ||
| // Preferred: use Assign to store, pass input through |
There was a problem hiding this comment.
Powers are written for agents, provide them with clear instructions when to use what. Use defaults and add overrides if necessary
| ### 1. Mixing JSONPath and JSONata fields in the same state | ||
| Invalid combinations: `Arguments` + `InputPath`, `Output` + `ResultSelector`, `Condition` + `Variable`. Remove all JSONPath fields from converted states. | ||
|
|
||
| ### 2. Forgetting to remove `.$` suffixes |
There was a problem hiding this comment.
Write this for agents, i.e. "Do not forget to remove .$ suffixes
| ✓ "orderId": "{% $states.input.orderId %}" | ||
| ``` | ||
|
|
||
| ### 3. Using `$` or `$$` instead of `$states` |
There was a problem hiding this comment.
Consider extracting full code examples to a snippets folder
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Incorporated feedback from the AWS Step Functions Dev team and SA team into the aws-step-functions power.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.