Invoice Engineering Productivity Workbench

Problem: engineering work often lacks reusable judgment criteria

When building invoice, finance, payment, or business-system changes, engineers often face PR reviews, design trade-offs, production errors, API contracts, and team standards. Relying on tribal knowledge can cause review comments that focus on style, design docs missing risks and rollback, debugging by guesswork, and repeated integration friction. This skill turns that work into executable templates and checklists, making output more structured.

How it works: trigger phrases route to capability modules

• Code review: input diff or PR; output a checklist and severity levels: blocking, suggested, optional.
• Technical design: input requirements and constraints; generate a template covering background, goals, choices, and risks.
• Debugging: input error message and context; produce a diagnosis tree, reproduction steps, and validation plan.
• Architecture trade-offs: input scenario and scale; compare benefits, applicability, and cost.
• API design: input resources and operations; output RESTful rules, field contracts, and error codes.
• Engineering standards: input language or framework; generate checklists and anti-pattern warnings.

The workflow emphasizes evidence and trade-offs: review correctness before style; reproduce, isolate variables, and inspect logs and metrics before changing code; choose architecture that fits the current stage rather than overcomplicating early.

Boundaries: it is a methodology tool, not an execution system

It is useful for engineers, tech leads, and DevOps when preparing docs, designs, reviews, and investigations. It does not call paid services, does not process real secrets or credentials, and does not replace final merge or release decisions. Output quality depends on whether the input includes concrete users, scenarios, constraints, and business rules.