roadmap

Product Roadmap Command

Use the Product Manager agent to update and maintain the living ROADMAP.md document based on GitHub issues, user feedback, velocity data, and strategic priorities.

Living Document: docs-internal/planning/ROADMAP.md Last Updated: Check file header Review Cycle: Weekly (Monday) and after each release

Usage Examples

# Update roadmap with current state (standard weekly review)
/roadmap

# Include detailed GitHub issues analysis
/roadmap --analyze-issues

# Focus on specific upcoming version
/roadmap --version=4.20.0

# Review and adjust priorities
/roadmap --review-priorities

# Generate strategic quarterly view
/roadmap --quarterly

Command Implementation

I'll update the living ROADMAP.md document using Product Manager agent analysis:

Step 1: Read Current Living Documents

echo "=== Reading Living Documents ==="

# Read current roadmap state
!cat docs-internal/planning/ROADMAP.md

# Read current priorities
!cat docs-internal/planning/PRIORITIES.md

# Read velocity tracking data
!cat docs-internal/planning/VELOCITY-TRACKING.md

# Get recent releases
!git log --oneline --since="1 month ago" | grep -E "(Release|release)" | head -10

Step 2: Analyze GitHub Issues & Community Feedback

echo "=== Analyzing Community Input ==="

# Get open issues by label
!gh issue list --state=open --limit=30 --json number,title,labels,createdAt,comments

# Get recent discussions
!gh api repos/{owner}/{repo}/discussions --jq '.[] | select(.category.name == "Ideas") | {number, title, comments}'

# Check for high-engagement issues
!gh issue list --state=open --json number,title,comments --jq 'sort_by(.comments) | reverse | .[0:5]'

Step 3: Product Manager Roadmap Update

I'll use the Product Manager agent to update the living roadmap:

Use the product-manager agent to update the living ROADMAP.md document:

**Context**:
- Current ROADMAP.md, PRIORITIES.md, VELOCITY-TRACKING.md (already read)
- Recent GitHub issues and community feedback (already analyzed)
- EdgarTools mission: Simple yet powerful, accurate financials, beginner-friendly, joyful UX, beautiful output
- AI-assisted velocity: 2-10x faster than traditional development

**Your Task**:

## 1. Review "Recently Completed" Section
- Verify v4.19.1 and v4.19.0 are properly documented
- Check if any older completions should be archived
- Ensure timeline and outcomes are accurate

## 2. Update "Critical Bugs (Point Releases)" Section
- Check current state: "None currently" or active critical bugs?
- If new critical bugs from GitHub, add to "Pending Point Release 4.19.X" subsection
- Follow format: Issue #XXX, severity, impact, timeline

## 3. Review Upcoming Version Sections (v4.20.0, v4.21.0, Q1 2026)
- Check if queued features from PRIORITIES.md are reflected
- Verify priority scores and estimates are current
- Add any new HIGH priority features from recent issues
- Remove or demote features that are no longer relevant

## 4. Assess Backlog Section
- Review lower priority items
- Add new MEDIUM/LOW features from recent GitHub activity
- Archive features with no user demand or superseded by better approaches

## 5. Strategic Adjustments
Based on:
- **Velocity data**: Are we on track? Adjust timelines if needed
- **User feedback**: Are we addressing highest-value requests?
- **Market positioning**: Are we strengthening core differentiators?

## 6. Update Metadata
- Update "Last Updated" date
- Set "Next Review" date (weekly Monday or after releases)
- Update velocity numbers if changed

**Output**:
Provide the specific sections of ROADMAP.md that should be updated, with exact markdown text to add/change/remove.

**Important**:
- Maintain existing structure and format
- Reference PRIORITIES.md for work queue alignment
- Reference VELOCITY-TRACKING.md for AI multipliers
- Keep user-focused language (avoid internal jargon)
- Maintain version numbering consistency