Customer Signal Review
Synthesizes recent interviews, tickets, reviews, calls, and notes into evidence-linked themes and product implications.
Product discovery, requirements, roadmaps, KPIs, and planning assets.
Synthesizes recent interviews, tickets, reviews, calls, and notes into evidence-linked themes and product implications.
Derive a complete, source-traceable inventory of applications, views, subviews, overlays, modes, and required states from a PRD or functional requirements. Use for product-surface planning, information architecture, UX scope, wireframe coverage, or design handoff. Do not use when the requested output is the wireframes or a design-tool generation prompt.
Derive a complete, source-traceable inventory of applications, views, subviews, overlays, modes, and required states from a PRD or functional requirements. Use for product-surface planning, information architecture, UX scope, wireframe coverage, or design handoff. Do not use when the requested output is the wireframes or a design-tool generation prompt.
Turn strategy and constraints into a sequenced feature roadmap with assumptions, dependencies, risks, and measurable outcomes. Starts from outcomes and themes, checks candidate features against capacity and dependencies, sequences into Now, Next, and Later horizons with confidence that decays with distance, attaches a riskiest assumption and a validation step to each item, defines outcome metrics with baseline, target, and review date, and produces separate internal and customer-safe views plus change triggers. Use when someone asks to build or revise a product or feature roadmap, sequence a backlog over quarters, show how features map to strategy, or explain what changes if capacity or priorities shift. Do not use for ranking items by score (use prioritization-rubric), sizing effort (use project-estimator), or mapping dependencies in depth (use dependency-map).
Turns strategy and constraints into a sequenced feature roadmap with assumptions, dependencies, risks, and measurable outcomes.
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Write Jira-ready epics and stories as paste-ready drafts with acceptance criteria, dependencies, release notes, and implementation handoff notes. Frames the epic around an outcome and success measure, slices work into vertical stories that pass an independence and testability check, writes Given/When/Then or rule-based acceptance criteria, records dependency links with owners, drafts user-facing release notes, and adds handoff notes for engineers, design, and QA. Use when someone asks to turn a feature, spec, or discovery notes into a Jira epic, write user stories with acceptance criteria, break an epic into tickets, or draft release notes for planned work. Do not use for deriving API and data requirements (use technical-requirements-splitter), sizing the work (use project-estimator), or uploading test evidence to a ticket (use jira-evidence-uploader).
Writes Jira-ready epics and stories with acceptance criteria, dependencies, release notes, and implementation handoff notes.
Build a KPI tree that connects a strategic goal to an outcome metric, controllable input metrics, guardrails, owners, and instrumentation. Use for product strategy, metric design, OKR measurement, north-star decomposition, initiative prioritization, or diagnosing why a business outcome is moving.
Build a KPI tree that connects a strategic goal to an outcome metric, controllable input metrics, guardrails, owners, and instrumentation. Use for product strategy, metric design, OKR measurement, north-star decomposition, initiative prioritization, or diagnosing why a business outcome is moving.
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Build a clear, defensible prioritization rubric using impact, effort, confidence, risk, strategic fit, and customer evidence. Defines the decision and gates, chooses three to six criteria tied to goals, writes anchored 1-5 scales, sets and tests weights, scores confidence separately from value, divides by effort, ranks, checks rank stability against weight changes, and records overrides and a recalibration cadence. Use when someone asks how to rank features, projects, or requests, wants a scoring model such as RICE or weighted scoring adapted to their context, needs to settle a prioritization dispute, or wants to score a backlog consistently. Do not use for sequencing ranked work into a timeline (use feature-roadmap), sizing the work (use project-estimator), or summarizing raw customer feedback (use synthesize-product-feedback).
Builds a clear prioritization rubric using impact, effort, confidence, risk, strategic fit, and customer evidence.
Create, screen, research, and rank distinctive product, service, feature, platform, or company names. Use when the user wants naming strategy, creative naming territories, brainstormed candidates, competitive or company-name collision checks, preliminary trademark screening, domain-availability research, naming scorecards, or a decision-ready shortlist with rationales and risks.
Create, screen, research, and rank distinctive product, service, feature, platform, or company names. Use when the user wants naming strategy, creative naming territories, brainstormed candidates, competitive or company-name collision checks, preliminary trademark screening, domain-availability research, naming scorecards, or a decision-ready shortlist with rationales and risks.
Estimate project scope, effort, timeline, staffing, confidence, risks, and tradeoffs from requirements or discovery notes. Decomposes work into estimable pieces, gives each a three-point range, rolls ranges up with overhead and discrete risks into P50/P80/P90 effort, converts effort to calendar time using real capacity and the critical path, states a confidence grade with the unknowns that drive it, and offers scope, schedule, and staffing tradeoffs. Use when someone asks how long a project will take, how many people it needs, what it will cost in effort, how confident an estimate is, or what to cut to hit a date. Do not use for splitting requirements into technical work (use technical-requirements-splitter), tracking a running project's burn (use burndown-diagnosis), or logging and scoring risks on their own (use risk-register).
Estimates project scope, timeline, staffing, confidence, risks, and tradeoffs from requirements or discovery notes.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
Stakeholder Synthesis workflow that groups context collection, production, review, and packaging tasks into one deliverable.
Turn product feedback from interviews, tickets, reviews, surveys, sales notes, or usage evidence into traceable themes, segment-specific insights, prioritized opportunities, and a research follow-up plan. Use for voice-of-customer synthesis, feedback analysis, churn-reason analysis, or deciding what product problem to investigate next. Do not use to treat anecdotes as demand, invent prevalence, or convert feedback directly into an implementation roadmap.
Turn product feedback from interviews, tickets, reviews, surveys, sales notes, or usage evidence into traceable themes, segment-specific insights, prioritized opportunities, and a research follow-up plan. Use for voice-of-customer synthesis, feedback analysis, churn-reason analysis, or deciding what product problem to investigate next. Do not use to treat anecdotes as demand, invent prevalence, or convert feedback directly into an implementation roadmap.
Split product requirements into traceable technical requirements, API needs, data model changes, and rollout constraints. Classifies each product statement, derives numbered technical requirements with acceptance checks, specifies API changes by resource, operation, compatibility class, and error behavior, plans data changes with an expand-and-contract migration path, records rollout ordering, flags, and rollback limits, and keeps a requirement-to-work traceability matrix with open questions. Use when someone asks to turn a PRD, user stories, or a feature brief into technical requirements, what API or schema changes a feature needs, or what constrains its rollout. Do not use for sizing the result (use project-estimator), writing Jira epics and stories from it (use jira-epic-writer), or choosing the system architecture (use technical-architecture).
Splits product requirements into technical requirements, API needs, data model changes, and rollout constraints.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback