Payments

Contract

• Input: problem or task defined by the skill body.
• Output: Markdown artifact or structured result with completion criteria met.
• Side effects: none (design/review/documentation only unless explicitly stated).
• Dependencies: none (self-contained unless linked to other skills).
• Stop condition: all process steps completed; artifact saved; criteria checked.
• Risk: low.
• Boundary: produces reasoning or documentation artifacts; does not modify external systems unless explicitly instructed.

Payments

Use this skill when money moves through the system. It should keep the seam small, the trust boundary explicit, and the failure and reconciliation story visible before implementation begins.

Contract

• Input: payments brief, money flow, and risk constraints.
• Output: payment seam proposal, reconciliation guidance, and failure/rollback posture.
• Scope: design the money-flow shape, not the full implementation.
• Rule: make settlement, retries, and reconciliation explicit.
• Rule: prefer the narrowest seam that still respects financial correctness.
• Rule: call out where manual review or operator intervention is required.

Steps

1. Identify the funds flow and trust boundary.
2. Decide how retries, idempotency, and settlement are handled.
3. Define the reconciliation path and operator responsibilities.
4. State the rollback or compensation posture clearly.

Completion criteria

• the funds-flow seam is named
• the reconciliation path is named
• the failure posture is explicit