Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no decisions, work out where a recurring problem keeps failing to surface, or cut a review structure that has grown past what it informs.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Every organization has a cadence. Most have one that accumulated — a meeting added after each incident, none ever removed — rather than one that was designed. The symptom is familiar: full calendars, thorough reporting, and decisions that still take six weeks.
A review that only shares information is a document pretending to be a meeting. Before a meeting recurs, answer three questions: what decision does this forum make, who in the room can make it, and what would have to be true for the answer to be no.
If a forum has made no decision in a quarter, either it is the wrong forum or the decision is being made elsewhere. Both are worth knowing.
The common failure is a monthly review that fills with weekly firefighting, so nobody ever looks up. The fix is not discipline in the room; it is a functioning weekly meeting that leaves nothing urgent for the monthly one to absorb.
The same metric presented two ways in two forums will be argued about in both. Each metric needs a single definition, a single source, and one named owner who is accountable for the number rather than for the outcome it measures — those are different people surprisingly often, and the distinction stops reporting from becoming advocacy.
Publish the pack before the meeting and expect it read. A review that spends its first half being presented to has cut its own decision time in half.
Most organizations can describe how information flows up. Far fewer can describe how long it takes, and the duration is the part that matters. A problem visible on Monday at the front line that reaches a decision-maker at the monthly review has lost three weeks to structure.
Define what jumps the cadence: thresholds that trigger immediate escalation regardless of the calendar, and who can pull that lever without asking permission. Then check that it has been used. An escalation path nobody has ever invoked is either a very healthy operation or a dead letter, and the second is more common.
Add a review and it lives forever; the calendar only grows. Review the cadence itself once a year: what each forum decides, whether it still decides it, and what could be merged or ended. Expect to remove something every time.
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.
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
The English summary is being prepared. Showing the original description.
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
The English summary is being prepared. Showing the original description.
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
The English summary is being prepared. Showing the original description.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
The English summary is being prepared. Showing the original description.
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
The English summary is being prepared. Showing the original description.
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
The English summary is being prepared. Showing the original description.