Results for “ma”

Run a user story mapping workshop with adaptive questions and a structured map output, generating backbone activities, user tasks, and release slices for a workflow.

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Turns a raw feature or project idea into a structured product plan document covering goals, audience, requirements, and constraints, with a maturity-tracking workflow.

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.

Turn a product idea into a manual-first process you can start delivering today, before writing any code.

Breaks a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

Guide product managers through breaking down epics into user stories using the Humanizing Work methodology with 9 splitting patterns.

Generates a structured Product Requirements Document for the MÄÄK dating app, with clarifying questions, right-sized user stories, and verifiable acceptance criteria.

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

Takes a high-level feature from an Epic and generates a detailed Product Requirements Document (PRD) in Markdown, covering goals, user stories, requirements, and acceptance criteria.

Provides strategic and operational guidance on ITIL 4 and ITIL 5 frameworks, focusing on AI governance, sustainability, and product-centric lifecycle management.

Generate a step-by-step construction plan from a one-line objective, with dependency graphs, parallel step detection, and adversarial review for multi-session engineering projects.

Generate a comprehensive product strategy using the 9-section Product Strategy Canvas, covering vision, market segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.

Guides the agent to act as a product manager, collecting context, proposing three requirement plans (bug fix, new feature, iteration), scoring them by ROI, and recommending one with an MVP slice and timeline.

Turns a raw idea into four linked planning files through a five-phase pipeline: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with kill criteria.

Build a minimum viable product using the minimalist entrepreneur approach: manual first, then processized, then productized.

Creates product backlog items in Why-What-Acceptance format, producing independent, valuable, testable items with strategic context.

Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.

Drafts a GitHub issue with YAML frontmatter and checkboxes, writing it to a local file for review.

Creates and manages Product Requirements Documents (PRDs) with structured user stories, acceptance criteria, and progress tracking for feature planning.

Provides frameworks for both acquiring companies and being acquired, covering strategic rationale, due diligence, valuation, integration, and negotiation.

Generate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria, with descriptions, design links, and acceptance criteria.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Structures product requirements into a single-page spec with problem, success metrics, scope, user stories, design notes, and rollout plan.

Guides the agent through structured protocols for writing technical specifications, implementation plans, and summaries, with file naming and task directory conventions.

Create a comprehensive Product Requirements Document using an 8-section template covering problem, objectives, segments, value propositions, solution, and release planning.

Generates comprehensive GitHub project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated issue tracking.

Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning to decide whether it deserves investment or recommendation.

Translates high-level ideas into detailed Epic-level Product Requirements Documents (PRDs) that serve as the single source of truth for engineering teams.

Verifies each step of a rough implementation plan against source code and current documentation, attaching proof and marking steps as verified or unverified.