Planning & Roadmapping helps you transform validated insights and strategic thinking into executable plans. Create comprehensive Product Requirements Documents (PRDs) and visualize your roadmap on a timeline to keep stakeholders aligned and teams focused.
What is Planning & Roadmapping?
Planning & Roadmapping encompasses two core planning features:
Product Requirements Documents (PRDs): Structured documents that outline what you're building, why you're building it, who it's for, and how success will be measured. PRDs connect your research, personas, markets, and solutions into a comprehensive plan.
Roadmaps: Visual timeline representations of when features and initiatives will be delivered. Roadmaps help you communicate plans, manage dependencies, and track progress across multiple initiatives.
These features help you bridge the gap between strategic thinking and tactical execution, ensuring your team builds the right things at the right time.
How to Access Planning Features
Navigate to planning features from the main sidebar:
PRDs - Create and manage Product Requirements Documents
Roadmapping - Visualize and manage your product roadmap
Product Requirements Documents (PRDs)
PRD Editor
What is a PRD?
A Product Requirements Document (PRD) is a comprehensive document that outlines:
What you're building (features, capabilities, scope)
Why you're building it (business objectives, user needs)
Who it's for (target markets, personas)
When it will be delivered (timeline, milestones)
How success will be measured (metrics, KPIs)
PRDs in Castspells.io are dynamic documents that link directly to your existing research, personas, markets, solutions, and tasks - ensuring your plans stay connected to validated insights.
Enter a name for your PRD (e.g., "Q1 2025 Mobile App", "Payment Integration", "User Dashboard v2")
Click Create
Your PRD will be created with a default template including common sections like Overview, Target Market, Target Personas, Goals & Success Metrics, Requirements, Roadmap, and Related Data.
PRD Structure and Sections
PRDs are built from flexible sections that you can add, remove, and reorder to match your workflow:
Section Types
Text Sections: Free-form rich text content for descriptions, requirements, specifications, and any other written content. Perfect for:
Product overview and vision
Goals and success metrics
Functional and non-functional requirements
Technical specifications
Launch plans and go-to-market strategy
Data Sections: Link to existing entities from your workspace like Hypotheses, Solutions, Tasks, Insights, and more. These sections automatically stay in sync with your data.
Market Sections: Display comprehensive market information including size, growth rate, customer segments, and key trends. Links directly to your Market Research.
Persona Sections: Show detailed persona information including demographics, goals, frustrations, and behavioral patterns. Links to your Customer Voice personas.
Roadmap Sections: Embed roadmap timelines showing scheduled initiatives, their timelines, and current status. Links to your Roadmapping data.
Working with PRD Sections
Adding Sections
Click the Add Section button between any existing sections or at the end of your PRD. Choose from:
Text Section: Add descriptive content, requirements, or specifications
Data Section: Link to hypotheses, solutions, tasks, or insights
Market: Display market research data
Persona: Show persona details
Roadmap: Embed roadmap timeline
Editing Sections
Text Sections: Click into the text area to edit using the rich text editor. Format text, add lists, include links, and structure your content.
Entity Sections: Use the selector buttons to add or change linked entities:
Data Sections: Search and select from your hypotheses, solutions, tasks, and insights
Persona Sections: Select a persona from your Customer Voice
Roadmap Sections: Pick a time range to display roadmap items
Removing Sections
Click the delete button in the section header to remove a section. This only removes it from the PRD - it doesn't delete the underlying data.
PRD Features
Timeline
Set start and end dates for your PRD to indicate the planning period. This appears in the PRD details section and helps teams understand the timeframe for delivery.
Lock/Unlock
Lock your PRD to prevent accidental edits during review or after approval:
Unlocked: Anyone with access can edit the PRD
Locked: PRD is read-only; editing is disabled
Toggle the lock status using the lock icon in the header.
Print to PDF
Generate professional PDF versions of your PRD:
Click the Print icon in the PRD header
Use your browser's print dialog
Choose "Save as PDF" as the destination
Configure paper size and margins as needed
The PRD is automatically formatted for print with:
Clean layout optimized for reading
High-contrast text and borders
All linked data displayed inline
Page breaks at logical points
PRD Best Practices
Research-Backed PRDs
Connect your PRD to validated research and data:
Link to Market Research: Use Market sections to ground your PRD in market reality
Reference Personas: Use Persona sections to make the target user explicit
Include Validated Hypotheses: Use Data sections to link to validated Hypotheses
Connect Solutions: Link to Solutions that address validated opportunities
Track with Tasks: Reference Tasks to show implementation progress
This ensures your PRD is based on evidence, not assumptions.
Keep PRDs Focused: Create separate PRDs for distinct initiatives rather than one massive document. This makes them easier to review, approve, and execute.
Update Regularly: Because PRD sections link to live data, they stay current automatically. Update text sections as plans evolve.
Use Templates: Create a PRD with your preferred structure, then duplicate it for new initiatives to maintain consistency.
Share with Stakeholders: Use the print/PDF feature to share PRDs in meetings and reviews. The read-only format is perfect for alignment discussions.
Roadmapping
Roadmap Timeline View
What is a Roadmap?
A roadmap is a visual timeline that shows when initiatives, features, and tasks will be delivered. Roadmaps help you:
Communicate plans to stakeholders
Visualize dependencies between initiatives
Track progress across multiple workstreams
Adjust timelines as priorities change
Coordinate work across teams
Castspells.io roadmaps are dynamic and connected - they automatically reflect changes to linked Hypotheses, Solutions, and Tasks.
Roadmap Structure
Roadmaps are organized with:
Lanes: Horizontal rows that group related work. Common lane types include:
Teams (e.g., "iOS Team", "Backend Team", "Design")
The item appears on your roadmap and can be moved or resized.
Moving and Resizing Items
Change Timeline: Drag the left or right edge of an item to adjust start or end dates.
Move Between Lanes: Drag an item up or down to reassign it to a different lane.
Reposition: Drag an item left or right to change when it starts while maintaining its duration.
Filtering the Roadmap
Use filters to focus on specific parts of your roadmap:
Date Range: Show only items within a specific time period
Lane: Display only specific lanes
Entity Type: Filter to show only hypotheses, solutions, or tasks
Status: Show items by their current state
Integrating Roadmaps with PRDs
Roadmap sections in PRDs automatically embed roadmap timelines:
Open a PRD in edit mode
Add a Roadmap section
Select a time range (e.g., "Q1 2025", "Next 6 months")
The roadmap for that period is embedded in your PRD
This keeps your PRD and roadmap in sync - changes to roadmap items automatically appear in the PRD.
Roadmap Best Practices
Start with Validated Work: Only add Hypotheses that have been validated or Solutions backed by research to your roadmap. Don't roadmap assumptions.
Use Lanes Strategically: Choose a lane structure that matches how you organize work. Team-based lanes work for resource planning; theme-based lanes work for strategic communication.
Keep It Current: Update roadmap items as timelines change. Because items link to live data, status updates happen automatically.
Show Dependencies: Place dependent items in sequence on the timeline. Consider creating a "Dependencies" lane for work that blocks other initiatives.
Communicate Frequently: Share roadmap views in planning meetings, stakeholder reviews, and team syncs to keep everyone aligned.
Account for Uncertainty: Use longer timeframes for later items. Near-term work should be detailed; future work can be approximate.