solve

Automate fintech-aware problem solving with governance gates and audit logging.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/sswapnil2/ai-config-fintech --skill solve-sswapnil2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solve
Source: https://github.com/sswapnil2/ai-config-fintech/tree/main/skills/solve
Command: npx skills add https://github.com/sswapnil2/ai-config-fintech --skill solve-sswapnil2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Default problem-solving loop for this org. It wraps obra/superpowers with fintech-specific gates to ensure security, governance, and auditability before changes are implemented.

Core Features & Use Cases

  • Fintech gate before implementation, including security review, audit-log verification, and payment-module gating when applicable.
  • Structured problem-solving lifecycle: Frame, Brainstorm, Plan, Isolate, Implement, Verify.
  • Compliance-ready tracking: logs decisions and enforces governance to keep audits clean.

Quick Start

Invoke the solve workflow on a non-trivial problem statement to apply fintech gates and orchestrate the end-to-end problem-solving loop.

Frequently Asked Questions about solve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce security review and audit logging for fintech feature migrations?

A structured problem-solving workflow automates fintech-grade governance by applying security review and audit-log verification gates before implementation. It frames the problem, plans changes, and verifies compliance for payment modules and PII.

What is the structured problem-solving lifecycle for multi-file changes touching PII?

The lifecycle for PII-touching multi-file changes includes six stages: Frame, Brainstorm, Plan, Isolate, Implement, and Verify. It isolates changes using git worktrees and iterates with test-driven development to ensure compliance.

Can I use test-driven development with git worktrees for payment-module gating?

Yes, the workflow isolates changes in a git worktree during implementation and iterates using test-driven development, verifying payment-module gating and audit-logging before completion.

Does the governance workflow support audit-log verification for auth changes?

Yes, the governance workflow enforces a fintech gate that includes audit-log verification and security review before implementing auth changes. It logs decisions to keep audits clean and ensure compliance.

When do I need a fintech gate before implementing non-trivial feature work?

You need a fintech gate before implementing non-trivial feature work when changes touch payments, auth, or PII. This gate enforces security review, audit-log verification, and payment-module gating to maintain auditability.