Filter Account Dropdown Entry Workflow

Requirement

Use this skill to help maintainers and users asking for software improvements with:

[Enhancement] Filter Account Dropdown in New Entry Form Based on Selected Payment Method

Read references/requirement-plan.md when source evidence, planning details, or review criteria are needed.

Workflow

1. Restate the user's outcome, constraints, available inputs, and success criteria.
2. Convert the request into a practical plan and useful output.
3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.
4. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.
5. Validate the output against the success criteria and list any remaining risks or follow-up work.

Expected Outputs

• A tailored answer or artifact for the user's immediate situation.
• A reusable checklist or workflow when the task is repeatable.
• A verification note showing how the result was checked.

Validation

• The output directly addresses the discovered requirement.
• The user can act on the result without reading the original source post.
• Assumptions, limits, and required inputs are visible.
• The final response includes a short usage or next-step note when helpful.

Triggers

Keywords: general-help, enhancement, filter, account, dropdown, entry, form, based, selected

Example trigger sentences:

• Help me [Enhancement] Filter Account Dropdown in New Entry Form Based on Selected Payment Method.
• I need a practical workflow for [Enhancement] Filter Account Dropdown in New Entry Form Based on Selected Payment Method.
• Use $filter-account-dropdown-entry-workflow to handle [Enhancement] Filter Account Dropdown in New Entry Form Based on Selected Payment Method.