Turn an app idea or existing repo into a PRD, UX/UI spec, MVP backlog of epics and user stories, and agent rules before Claude Code, Cursor or Codex writes code. Built for solo builders and vibe coders.
Prüft Akzeptanzkriterien auf Klarheit, Testbarkeit und Vollständigkeit. Liefert priorisierte Lücken, Risiken und konkrete Verbesserungen für Produkt- und Projektteams.
Find the requirements engineering would otherwise be forced to guess. Audit a PRD or feature specification for ambiguity, hidden assumptions, missing acceptance criteria, unresolved dependencies, edge cases, scope gaps, proxy metrics, and decisions that have not actually been made. Use it before implementation starts — while fixing the specification is still cheaper than fixing the product.
Produces a prioritized Now / Next / Later roadmap from a strategy, candidate initiatives, and team capacity — with promotion/kill criteria and dependency flags. Use when the user says "prioritize our roadmap", "help with quarterly planning", "what goes on the roadmap", "review our roadmap priorities", or "build a theme-based roadmap". Do not use when the request is turning a spec into individual tickets.
Turns a raw idea or an existing PRD into a proceed / descope / kill verdict, using isolated bull-case and bear-case reviews after you commit your own take first.
Turns a half-formed idea into a full PRD with problem statement, user needs, requirements, success metrics, and open questions. Use when the user says write a PRD, needs a product requirements document, wants to turn an idea into a spec, or is scoping a feature spec. Do not use when they want a design doc for already-approved requirements, not requirements discovery.
Produces a theme-based product roadmap organized Now / Next / Later, with quarterly OKR or outcome-based variants, from scattered goals and backlog items. Use when the user says "build our product roadmap", "turn this backlog into a roadmap", "create a now next later plan", "quarterly roadmap for stakeholders", or "prioritize our features". Do not use when the request is a single sprint plan.
Scores and ranks candidate features using RICE — reach from real data, impact anchoring, confidence ceilings, builder effort estimates — plus a sensitivity/flip analysis. Use when the user says score these features with RICE, prioritize backlog by RICE, run a RICE scoring session, or sensitivity-test our ranking. Do not use for a multi-framework prioritization comparing RICE, MoSCoW, and Kano.
Scores and prioritizes LLM and AI use cases by business value, effort, risk, data readiness, process readiness, implementation complexity, stakeholder fit, governance needs, and expected operational impact, helping businesses create practical AI adoption roadmaps instead of pursuing random experiments.