Results for “routes”

Routes founder questions to the right advisor roles, coordinates multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions.

Use when a high-priority signal needs to reach the operator but doesn't fit the current conversation (off-hours wake, urgent error needing eyes, scheduled-tick discovery worth surfacing now). Routes via MIMIR_OPERATOR_ALERT_CHANNEL.

Routes enterprise architecture tasks to specialized sub-skills covering strategy, business, data, governance, solution, and technology architecture, with a focus on frameworks like TOGAF and Zachman.

Routes commercial inquiries to specialized sub-skills for pricing, deal desk, partnerships, channel economics, policy, RFP response, and forecasting. Provides deterministic decision support with canon-cited analysis and human-approver routing.

Routes research planning, funding, scoping, and synthesis inquiries to one of four sub-skills: clinical research, R&D finance, market research, or product research, using a deterministic decision tree.

Reverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.

Routes product requests to one of 12 bundled skills covering prioritization, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, and SaaS scaffolding.

Architecture discovery for Sage/Acorn projects — map existing codebase, discover post types, routes, ACF field groups, Livewire components, Service Providers, identify architectural gaps, architecture decision records, ADR, component boundary map, data flow diagram, risk register, implementation sequencing, discovery session, understanding unknown codebases, use before architecting or building new features, output contract, discover-abilities

Turn assumptions, funnel opportunities, and product questions into a prioritised, feasibility-checked experiment backlog. Filters by traffic reality, metric latency, and method feasibility — not just ICE/RICE scoring. Maintains a living portfolio with status (idea → designed → running → readout → archived). Load when the user says "what should we test next", "build an experiment backlog", "prioritise our tests", "where should we experiment", "what's worth testing", or when the experimentation orchestrator routes here.

Set a deliberate visual direction before any UI is built — the single biggest lever against generic AI output. Derives a posture from product-soul/PRD/specs, scores a curated archetype palette, then generates 2-3 GENUINELY DISTINCT directions and compares them side-by-side before committing to one. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, explore visual options, says "what should this look like", "make it feel like [Linear/Apple/ Duolingo]", "give me design directions", "explore some looks", or when frontend-design routes here. Replaces design-archetype. Sub-skill of frontend-design.

Orchestrator + builder for distinctive, production-grade frontends that don't look AI-generated. Derives stack and design context from product-soul/PRD/specs, then runs the anti-slop chain — explore distinct directions, lock a DESIGN.md system, build from golden examples with mandatory polish + every interactive/empty/loading/error state, then review. Load when the user asks to build a UI, design a frontend, build a landing page or dashboard or web app, beautify or redesign a page, make a UI look premium/playful/editorial, says "build me a frontend", "make this not look AI-generated", "design this interface", "give this real polish", or "frontend design". Routes to design-direction, design-system, design-review.

Orchestrator for the experimentation skill suite — turn assumptions and product questions into rigorous, well-instrumented experiments and decision-grade readouts. Routes through backlog → spec → runbook → readout based on user need and existing artefacts. Platform-agnostic with PostHog as the primary binding. Load when the user asks to design an experiment, A/B test something, set up an experiment, run a holdout, test a hypothesis, decide what to test next, read out experiment results, analyse a test, or says "should we A/B test this", "experiment on the landing page", "is this lift real", "ship or kill this test", "what should we test next", "build an experiment backlog", "test the pricing page", "validate this with an experiment".

Build, audit, debug, and migrate websites for durable organic discovery and reliable use by search engines, LLMs, and browser agents. Use for SEO audits or implementation; new sites, routes, templates, CMSs, catalogs, or content programs; crawling, rendering, indexing, robots, canonicals, redirects, sitemaps, hreflang, structured data, metadata, links, faceted navigation, JavaScript SEO, Core Web Vitals, or migrations; keyword, intent, architecture, content, local, media, or authority work; traffic, ranking, CTR, or indexation losses; AEO, GEO, AI Overviews, AI Mode, ChatGPT search, crawler controls, agent-readable pages, Markdown representations, `Accept: text/markdown` content negotiation, `llms.txt`, WebMCP, or agent interaction design. Trigger whenever code or architecture can materially affect public discoverability or machine usability, even if the user does not say SEO. Do not use for paid-search management alone.

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.

Orchestrator for the pre-decision business-idea lifecycle — generate ideas, model them, evaluate them, validate them with customers, and only then hand off to product-soul / brainstorming. Routes through `idea-generation`, `business-modeling`, `idea-evaluation`, and `customer-discovery`. Load when the user asks to explore business ideas, find a startup idea, evaluate a venture, validate an idea, says "what business should I start", "should I build this", "is this a good business", "I have a startup idea", "evaluate this venture", "model this business", "validate this idea", "Mom Test this", "Lean Canvas this", "Business Model Canvas", "Value Proposition Canvas", "go/no-go on this idea". Pre-decision suite — once one idea is committed, hands off to `product-soul`. Does NOT design features (use `brainstorming`) or audit built products (use `reality-check`).