roadmap-integration

<quick_start> <roadmap_workflow> Vision-aligned feature management:

1. Initialize: Verify GitHub authentication (gh CLI or GITHUB_TOKEN)
2. Load vision: Read docs/project/overview.md for alignment validation
3. Parse intent: Identify action (add, brainstorm, move, delete, search, ship)
4. Validate vision: Check against out-of-scope exclusions and project vision
5. Create issue: Generate GitHub Issue with metadata (area, role, slug)
6. Show summary: Display roadmap state and suggest next action

Quick actions:

/roadmap add "student progress widget"
/roadmap brainstorm "CFI productivity tools"
/roadmap move auth-refactor Next
/roadmap search export

Example workflow:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📋 VISION ALIGNMENT CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Project Vision:
AKTR helps flight instructors track student progress against ACS standards.

Proposed Feature:
  Add student progress widget showing mastery percentage by ACS area

✅ Feature aligns with project vision

Target User Check:
Does this feature serve: CFIs, Flight students, School admins
Confirm primary user (or 'skip'): Flight students

✅ Vision alignment complete

✅ Created issue #123: student-progress-widget in Backlog
   Area: app | Role: student

📊 Roadmap Summary:
   Backlog: 12 | Next: 3 | In Progress: 2 | Shipped: 45

Top 3 in Backlog (oldest/highest priority):
1. #98 cfi-batch-export (Created: 2025-11-01)
2. #87 study-plan-generator (Created: 2025-11-05)
3. #123 student-progress-widget (Created: 2025-11-13)

💡 Next: /feature cfi-batch-export

</roadmap_workflow>

<trigger_conditions> Auto-invoke when:

• /roadmap command executed
• User mentions "roadmap", "add feature", "brainstorm ideas", "prioritize features"
• Starting feature planning workflow

Prerequisites:

• GitHub authentication (gh CLI or GITHUB_TOKEN)
• Git repository with GitHub remote
• Optional: docs/project/overview.md for vision validation </trigger_conditions> </quick_start>

Verify GitHub authentication and repository access.

Actions:

• Check GitHub CLI authentication (gh auth status)
• Fallback to GITHUB_TOKEN environment variable
• Verify git repository has GitHub remote
• Source roadmap manager scripts

Script location: See references/github-setup.md for platform-specific bash/powershell scripts

Validation:

AUTH_METHOD=$(check_github_auth)  # Returns: gh-cli, token, or none
REPO=$(get_repo_info)             # Returns: owner/repo-name

if [ "$AUTH_METHOD" = "none" ]; then
  echo "❌ GitHub authentication required"
  echo "Options: gh auth login OR export GITHUB_TOKEN=ghp_..."
  exit 1
fi

Output:

✅ GitHub authenticated (gh-cli)
✅ Repository: owner/repo-name

Load project vision, scope boundaries, and target users from overview.md.

When to execute:

• Always before ADD/BRAINSTORM actions
• Skip for MOVE/DELETE/SEARCH operations

Actions:

PROJECT_OVERVIEW="docs/project/overview.md"
HAS_PROJECT_DOCS=false

if [ -f "$PROJECT_OVERVIEW" ]; then
  HAS_PROJECT_DOCS=true
  # Extract: Vision, Out-of-Scope, Target Users
  # (see detailed extraction logic in references)
else
  echo "ℹ️  No project documentation found"
  echo "   Run /init-project to create (optional)"
fi

Extracted context:

• Vision: 1 paragraph describing project purpose
• Out-of-Scope: Bullet list of explicit exclusions
• Target Users: Bullet list of intended users

See: references/vision-validation.md for extraction logic and validation rules