Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.adaline.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Strategic roadmaps take days to build and still end up misaligned between engineering, sales, and leadership. This prompt generates a full product roadmap — strategic overview, quarterly timeline, prioritised features, resource allocation, success metrics, and risk mitigation — from six inputs. Bring it into your next planning session instead of starting from a blank slide.

How the prompt works

The system prompt sets the LLM up as a product strategy consultant and requires six specific output sections in every response. Without that structure, models produce generic strategic advice instead of a document a cross-functional team can review and act on. The user prompt takes six variables that capture the full context of a planning cycle — product, goals, market conditions, constraints, timeline, and stakeholder priorities.

System prompt

Sets the LLM’s role and defines the six sections it must always include in the output.
You are an expert Product Strategy Consultant with deep experience in creating comprehensive product roadmaps for tech companies. Your task is to generate a strategic product roadmap that aligns business goals with market opportunities and resource constraints.

Create a roadmap that includes:

1. Strategic Overview: High-level vision and key objectives.
2. Quarterly Timeline: Clear phases and milestones.
3. Prioritised Feature List: Features ranked by impact vs effort with rationale.
4. Resource Allocation: Team assignments and capacity planning.
5. Success Metrics: KPIs for each quarter and feature release.
6. Risk Mitigation: Potential blockers and contingency plans.

Format the roadmap for easy cross-functional team review and executive alignment.

User prompt

Six variables that capture the full context of a planning cycle — product, goals, market conditions, constraints, timeline, and stakeholder priorities.
Generate a product roadmap for {{product_name}} with the following parameters:

- Strategic goals: {{strategic_goals}}
- Market trends: {{market_trends}}
- Resource constraints: {{resource_constraints}}
- Timeline: {{timeline_period}}
- Key stakeholders: {{stakeholder_priorities}}
Product roadmap: Q1–Q3 2025 strategic planStrategic overviewVision: Transform CloudSync into the leading hybrid cloud platform for enterprise and mid-market customers through AI-powered analytics and seamless scalability.Key objectives:
  • 30% improvement in customer retention
  • Mid-market segment penetration
  • Enhanced platform performance and compliance
Quarterly timelineQ1 2025 — Foundation and compliance Focus: Technical debt reduction and GDPR/SOC2 compliance
  • Database optimisation and performance tuning
  • Privacy compliance framework implementation
  • API rate limiting and security enhancements
  • Milestone: SOC2 certification achieved
Q2 2025 — AI integration and mid-market features Focus: Competitive differentiation and market expansion
  • AI-powered usage analytics dashboard
  • Simplified onboarding workflow for mid-market
  • Automated scaling capabilities
  • Milestone: Mid-market pricing tier launch
Q3 2025 — Scale and optimisation Focus: Retention improvement and advanced features
  • Predictive maintenance alerts
  • Advanced reporting suite
  • Mobile app for platform monitoring
  • Milestone: 30% retention improvement target
Prioritised feature list
  • P0: GDPR compliance — High impact, Medium effort — legal requirement and market necessity
  • P0: Performance optimisation — High impact, High effort — critical for customer retention
  • P1: AI analytics dashboard — High impact, High effort — key competitive differentiator
  • P1: Mid-market onboarding — Medium impact, Medium effort — revenue growth opportunity
  • P2: Mobile monitoring app — Medium impact, Low effort — resource permitting
Resource allocation
  • Q1: 4 backend (compliance), 3 frontend (UX improvements), 2 DevOps (infrastructure)
  • Q2: 6 frontend (AI dashboard), 3 backend (APIs), 2 DevOps (scaling)
  • Q3: Balanced allocation across retention features and optimisation
Success metrics
  • Q1: 40% performance improvement, SOC2 certification
  • Q2: 100 mid-market signups, 70% AI dashboard adoption
  • Q3: 30% retention increase, 4.5+ customer satisfaction score
Risk mitigation
  • Technical: AI implementation complexity → start with simple analytics and iterate
  • Resource: Engineering capacity constraints → prioritise P0 features, defer P2
  • Market: Competitive pressure → fast-track AI differentiation features

Import into Adaline

This prompt comes with a ready-to-import Adaline project file. It includes the prompt, dataset, and evaluators, all pre-configured.

Evaluations and dataset

Each prompt in the library ships with a dataset and evaluators so you can test quality before deploying.

Evaluators

Two failure modes, three evaluators: one for completeness, one for strategic alignment, one for length.

Roadmap completeness

Checks that all six required sections are present in every output.
Goal: The roadmap must include all six required sections.

Checks:
- Strategic Overview with vision and key objectives is present
- Quarterly Timeline with phases and milestones is present
- Prioritised Feature List with impact and effort rankings is present
- Resource Allocation across teams and quarters is present
- Success Metrics per quarter are defined and measurable
- Risk Mitigation with specific contingency plans is present

Scoring guidance:
- 1: Missing 3 or more required sections.
- 2: Missing 2 required sections.
- 3: All sections present but some are superficial or lack detail.
- 4: All sections present with good detail; minor gaps.
- 5: All sections fully present, well-structured, and detailed.

Strategic alignment

Checks that the roadmap directly reflects the stated goals, constraints, and stakeholder priorities.
Goal: The roadmap must directly reflect the stated strategic goals, resource constraints, and stakeholder priorities provided in the input.

Checks:
- Prioritised features directly address the stated strategic goals
- Resource allocation respects the stated team size and budget
- Timeline is scoped to the stated timeline period
- Stakeholder priorities are reflected in the feature list and quarterly focus
- Risk mitigation addresses constraints specific to the inputs, not generic risks

Scoring guidance:
- 1: Roadmap is generic — could apply to any product.
- 2: Some alignment with inputs but most content is generic.
- 3: Adequately aligned; minor disconnects between inputs and output.
- 4: Mostly aligned; small gaps in reflecting specific constraints or priorities.
- 5: Fully aligned — every section maps back to the stated goals, constraints, and stakeholder needs.

Response length

Guards against bloated output. A roadmap should be a planning tool, not a report.
Rule: Output must be less than 1,200 tokens.
A good roadmap is structured and scannable. If it’s too long, teams won’t use it as a reference.

Dataset

Four product types across different industries — each row maps directly to the six variables in the user prompt.
ProductStrategic goalsMarket trendsResource constraintsTimelineKey stakeholders
CloudSync: Enterprise PlatformIncrease enterprise retention by 30%, expand into mid-market, improve scalabilityGrowing demand for AI analytics, data privacy compliance, hybrid cloud shift12 engineers, $500K budget, 9-month timelineQ1–Q3 2025Sales needs faster onboarding, engineering wants to cut tech debt, marketing needs differentiation
MoneyMap: Personal Finance AppGrow MAU by 40%, launch premium subscription tier, improve budgeting accuracyOpen banking adoption, Gen Z financial literacy demand, rise of spend analytics8 engineers, $200K budget, 6-month timelineQ2–Q3 2025Growth team needs viral features, product needs retention hooks, compliance needs audit trail
SupplyHub: Procurement MarketplaceReduce buyer onboarding from 14 to 3 days, add supplier verification, expand to EUB2B marketplace consolidation, ESG compliance requirements, supply chain risk awareness10 engineers, $350K budget, 12-month timelineQ1–Q4 2025Ops needs automated matching, legal needs compliance tools, sales needs self-serve onboarding
DeployKit: CI/CD Automation ToolReduce mean deployment time by 50%, launch enterprise tier, improve pipeline observabilityDevOps platform consolidation, shift-left testing adoption, platform engineering trend6 engineers, $150K budget, 6-month timelineQ3–Q4 2025Engineering leads want faster deploys, DevOps wants better visibility, sales needs enterprise SSO