plan-connector-implementation

To create a payment connector implementation plan, provide your connector spec path to map API requirements to UCS architecture patterns and generate a standardized implementation approach with authentication, amount conversion, and status mapping details.

UCS pattern mapping translates API specifications into standardized architecture flows for payment connectors. It enforces flow classification against standard UCS flows to ensure reliable translation of specs into actionable architecture artifacts.

Validating API specs before code generation involves an interactive planning phase that checks flow classifications and architecture decisions. This ensures the spec maps correctly to UCS patterns before entering downstream coder-reviewer-tester loops.

Defining authentication and status mapping for new connectors requires mapping API requirements to UCS architecture patterns. This approach standardizes flow classifications and amount conversion to produce a comprehensive implementation plan document.

Bridging the gap between API specification and code generation requires creating detailed implementation plans with interactive validation. This maps API specs to UCS patterns and standardizes flow classifications to produce actionable architecture artifacts.

Planning payment connectors from API specs requires an existing spec file path and focuses on pre-code architecture planning. It does not generate code directly but produces a plan document to guide subsequent coder-reviewer-tester loops.