Results for “quarterly-review”

Guides a structured founder interview to capture company context across 7 dimensions, generating a persistent context file used by C-suite advisor skills.

Scores any US stock ticker through Warren Buffett's four-lens framework (business simplicity, moat, management, valuation) and returns a weighted HOLDABLE/WATCHABLE/AVOID verdict.

Analyzes earnings-season implied volatility: historical IV crush, implied move forecast, IV Rank strategy tag, and a priced Iron Condor quote ready to trade.

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)

Eng manager-mode plan review. (gstack)

Weekly engineering retrospective. (gstack)

Tracks team OKRs with quarter banner, objective columns, key result progress bars, owner avatars, and status pills.

Use to build an account's cumulative support record ahead of a renewal or QBR, so the review reflects the whole relationship rather than the most recent ticket. Trigger for "prepare for this renewal", "what has this account's support experience been", "which accounts are at risk before renewal", QBR preparation, account health review, or an account that renewed badly with no warning.

Review QML code for correctness, performance, and idiom using qmllint and Qt6 best practices.

Weekly engineering retrospective. (gstack)

Audits source code across C++, Android, iOS, and Web to classify files, detect embedded third-party libraries, and produce four-level verdicts with interactive HTML reports.

Weekly engineering retrospective. (gstack)

Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR/MR/CL, address review feedback, or prepare a change for submission.

Reviews code diffs or explicit file sets through independent correctness and QA lenses, producing a severity-ordered verdict for pre-merge audits or review gates.

Analyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Review the current branch's changes against the project's code style and

Compose a provider-neutral AI team by tiering accessible models on cost-efficiency, capability, latency, and governance, then mapping the 8 processkit role archetypes onto catalog Roles + RoleSlots inside a chartering Scope. Use when bootstrapping a new project team, rotating after a provider change, or quarterly rebalancing. Triggers: "create my AI team", "compose a team", "rebalance the team", "review the team".

Use to distil a CX dashboard into the three numbers a board or exec actually needs — volume/demand health, quality/outcome, and cost/efficiency — with commentary that drives decisions instead of forty tiles nobody acts on. Trigger for "board pack", "exec summary for support", "what should leadership see", "too many metrics on the dashboard", "three KPIs for the board", quarterly business review CX section, or when a leadership deck is mostly charts with no story.