Set up product work from goals, users, feedback sources, metrics, and decision owners.
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 before sorting feedback, scoring the roadmap, or writing a spec.
Ask for the company and product goals for this period, the main user types, the plans or segments that matter most, and the current roadmap. Ask for the feedback sources: tickets, sales notes, interviews, surveys, and reviews. Ask for the usage metrics and where they live. Record the system, owner, date range, and last refresh for each source.
Agree the prioritisation method the team trusts and who supplies effort estimates. Ask who decides what goes on the roadmap, who approves a spec, who approves release notes, and who may talk about dates with customers. Agree how a request is counted: by ticket, by account, or by revenue.
Give the user:
Never fill a gap in the data with a guess or a made-up quote. Do not edit the roadmap, tracker, or changelog, and do not promise a date to anyone.
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.