Sort feature requests by the problem behind them, who asked, how often, and what is missing.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this for a backlog of requests from customers, sales, or the team.
For each request note who asked, their plan and segment, the date, and the exact words. Ask what they were trying to do when they wanted it, what they do today instead, and how often. If the request does not say, mark the problem unknown rather than guessing it.
Merge requests that share a problem even when they ask for different solutions. For each merged item give:
Sort items into look closer, already planned, needs evidence, and not now, with a reason for each. Name who should follow up with which customer and what to ask.
Do not reply to customers, promise a feature, or change the tracker yourself; recommend and draft. Never invent a requester, a count, or a revenue figure.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.