Results for “ma”

Select the right Proof of Life (PoL) probe type based on hypothesis, risk, and resources to match validation method to the real learning goal.

Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations to reframe product decisions around user motivations.

Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations.

Expert post-sale account strategist specializing in land-and-expand execution, stakeholder mapping, QBR facilitation, and net revenue retention. Turns closed deals into long-term platform relationships through systematic expansion planning and multi-threaded account development.

Turn a generic product tour into a buyer-specific demo that only shows what they told you hurts. Maps every feature you plan to show to a problem the buyer actually stated, writes the "so what" for each moment, and flags the trap of feature-dumping before you fall into it. Built for B2B sales teams, customizable to your product and your discovery. Trigger on "build a demo script", "prep for the demo", "what should I show", "map features to pain", "stop me from feature dumping", or any pre-demo planning pass.

Analyze diverse user feedback to identify at least 3 distinct behavioral and needs-based user segments based on jobs-to-be-done, behaviors, and motivations.

Discovers and researches companies matching an ideal customer profile, using Browserbase Search API and a Plan→Research→Synthesize pattern to produce scored reports and CSV exports.

Transforms a raw product idea into four planning files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with kill criteria.

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language, with scoring and diagnostic tools for evaluating domain model quality.

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.

Conduct structured, multi-session brand identity interviews to produce a master brandbook covering purpose, positioning, audience, personality, voice, narrative, and founder-brand tension.

Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer.

Analyze customer needs by identifying the 'job' they hire a product to do, covering job statements, forces of progress, and competitive landscapes.

Uncover customer jobs, pains, and gains in a structured JTBD format to clarify unmet needs, reposition products, or improve discovery and messaging.

Designs and maintains versioned reusable task sequences in Financial Services Cloud using Action Plan templates for client onboarding, account opening, annual review preparation, and compliance tasks.

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

Maximize form completion rates for lead capture, contact, demo request, application, survey, quote, and checkout forms by diagnosing friction and applying evidence-based optimizations.

Guides agents through the full lifecycle of NeMo-RL experiments: understanding recipes, launching reproducible runs, analyzing results, and preserving human oversight with git and TSV logs.

Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, dedupe, relabel, reassign, and post summaries — all from the shell without clicking through the UI.

Create and maintain AI-agent integration files for Pump.fun SDK work, including AGENTS/CLAUDE/COPILOT/GEMINI instructions, .well-known discovery, LLM context docs, skills registries, MCP prompts, and terminal rules. Use when wiring agents to Pump.fun development workflows.

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

Compute fully-loaded cost-to-serve per channel, channel ROI under cash/LTV/marginal lenses, and optimal channel mix subject to strategic constraints for quarterly channel reviews.

Uses the filesystem as a durable overflow layer for agent context, enabling scratch pads, plan persistence, sub-agent communication, dynamic skill loading, and log management.

Orchestrates a full software development pipeline by sequentially loading and executing seven role-specific skills (BA, TechLead, PM, BE Dev, FE Dev, Tester, QA/QC), with configurable project levels and gate checks.

Customer insight specialist for audience understanding. Use when defining target audience, buyer personas, customer pains, value mapping, problem discovery, audience language. Triggers: 'who would buy this', 'target audience', 'buyer persona', 'customer pain points', 'ideal customer', 'user problems', 'value proposition', 'audience research'.

Manage R&D program budgets with F&A splits, track burn rate and runway against milestones, and route capitalize-vs-expense decisions to a named finance owner.

Pressure-test any business idea with a five-angle adversarial panel (Critic, Champion, Analyst, Investigator, Customer) that returns a single GO/RESHAPE/KILL verdict with the cheapest test to de-risk it.

Provides a suite of five product team skills covering OKR alignment, feature prioritization, sprint planning, user research, and design systems, with scripts and templates for each role.

Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.

Parse RFP/RFI/RFQ documents, score fit per requirement with verifiable proof points, generate win-themes, estimate winrate, and produce a bid/no-bid recommendation using the Shipley method.

Generates a Startup Canvas combining a 9-section Product Strategy with a Business Model for new products, offering an alternative to the Business Model Canvas and Lean Canvas.

Run customer interviews that uncover real problems using Mom Test rules: ask about their life, not your idea; focus on past specifics; and secure commitments instead of collecting compliments.

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria, focusing on user situations and outcomes for JTBD-style backlog items.