chore: remove deprecated powers and refresh README inventory - #201
Merged
Merged
Conversation
- Delete POWER.md documentation file - Delete mcp.json server configuration - Remove stripe-best-practices.md steering guide - Deprecate Stripe integration from available powers
…P configuration - Delete POWER.md with deprecation notice and migration guide - Remove mcp.json MCP server configuration file - Remove steering/steering.md workflow documentation - Consolidate functionality into AWS Observability power as planned - Clean up registry entry per deprecation timeline
- Update aws-amplify title to include "Gen2" for clarity - Correct aws-healthomics MCP server name from awslabs.aws-healthomics-mcp-server to aws-healthomics - Add aws-transform-mcp server reference (was previously "None") - Remove deprecated cloudwatch-application-signals power section - Revise databricks description to clarify optional MCP server support - Simplify dynatrace MCP server name to dynatrace - Add new kiro-support power with AWS Support case management capabilities - Capitalize neon MCP server name for consistency - Update power-builder description to reflect Agent Plugins specification support - Enhance stackgen description with additional capabilities and integrations - Remove stripe power section
Jay2113
approved these changes
Oct 1, 2026
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.
Summary
Removes two deprecated powers and brings
README.mdback in sync with what therepo actually ships.
Removed powers
POWER.md,mcp.json, and steering docs.[DEPRECATED]; itscapability was merged into the aws-observability power, which continues to
ship
awslabs.cloudwatch-applicationsignals-mcp-server. RemovedPOWER.md,mcp.json, and steering docs.README reconciliation
The power list had drifted from the directory contents:
kiro-support— present on disk but never listed. Description andMCP servers taken from its
plugin.json.stripeandcloudwatch-application-signalsentries.mcp.json:aws-healthomics(wasawslabs.aws-healthomics-mcp-server)dynatrace(wasdynatrace-mcp-server)Neon(wasneon)aws-transformwas listed as having no MCP server but shipsaws-transform-mcppower-builder(now describes its Agent Plugins work),databricks(MCPserver is optional),
stackgen(adds deployment runners and ServiceNow).aws-amplifyto "Build full-stack apps with AWS Amplify Gen2" tomatch its
displayName.Verification
README.md, and the READMEreferences no directory that does not exist: 31 directories, 31 entries,
one-to-one.
that power's
POWER.mdfront matter orplugin.json.Notes
Power count goes from 33 to 31. No other power directories were touched.