feat: add roadmap command definition

[adslaton]

Summary

• Add new roadmap command to the workflow category
• Provides strategic development roadmaps with phases, milestones, and context integration
• Distinct from plan this - focuses on strategic vision vs tactical implementation

Changes

• Created dictionary/workflow/roadmap.md with comprehensive command definition
• Updated main index to include roadmap in workflow commands section
• Added roadmap to quick reference table

Test plan

• Dictionary validation tests pass
• Markdown linting compliance
• All pre-commit hooks pass

🤖 Generated with Claude Code

[github-actions]

🔒 Security Scan Results

✅ npm audit - Dependency Security

No vulnerable dependencies found.

⚠️ audit-ci Security Check

No results file generated.

⚠️ ESLint Security Analysis

No results file generated.

---

✅ All security scans passed! No issues found.

[github-actions]

🤖 AI Review

Of course. Here is a review of the pull request, structured according to your request.

---

Pull Request Review

Summary of Changes

This pull request introduces a new roadmap command designed to generate strategic, high-level development roadmaps. The changes include:

1. A new, comprehensive markdown file (dictionary/workflow/roadmap.md) that defines the command, its expected output format, considerations, and context integration instructions.
2. Updates to information-dense-keywords.md to register the new roadmap command in the main list and quick reference table, placing it within the "Workflow" category.

The PR aims to fill a strategic planning gap, differentiating this command from the more tactical plan this command.

---

Strengths of the Implementation

This is an exceptionally well-crafted and thoughtful pull request.

1. Comprehensive Definition: The roadmap.md file is incredibly thorough. It covers not just the "what" but also the "why" and "how." Sections like Risk Assessment, Resource Requirements, Success Metrics, and Communication Plan provide a robust framework that will lead to high-quality, professional-grade outputs.
2. Clear Distinction: The PR description and the definition itself do an excellent job of distinguishing roadmap (strategic vision) from plan this (tactical implementation). This clarity is crucial for both users and the AI model to use the command correctly.
3. Excellent Structure: The expected output format is well-structured and mirrors real-world project management artifacts. Using markdown headers, lists, and even an ASCII timeline provides a strong, clear template for the AI to follow.
4. Context-Awareness: The Context Integration section is a critical and well-executed feature. It explicitly instructs the AI on how to analyze provided files to create a relevant and grounded roadmap, moving beyond generic templates.
5. Ecosystem Integration: The inclusion of Related Commands (plan this, spec this, etc.) is a fantastic best practice. It helps users discover related functionality and encourages a logical workflow from high-level strategy down to detailed specifications.

---

Issues or Concerns

There are no major bugs or blocking issues. The concerns are minor and related to potential flexibility and refinement.

1. Rigidity of the Template: The example output is very detailed. While this is primarily a strength, it might be overly prescriptive for simpler requests. For example, a user asking for a roadmap for a small new feature might not need a full Executive Summary, Current State Assessment, and Communication Plan. The model might produce an output that feels too heavyweight for the request.
2. Hardcoded Timelines: The example phases have fixed timeframes (e.g., "Months 1-3", "Months 4-6"). This might lead the model to overuse these specific durations, even when a project's scope suggests a different timeline (e.g., a roadmap spanning several years or just a few weeks).

---

Suggestions for Improvement

These are minor suggestions that could make this already excellent contribution even better.

1. Add Flexibility Guidance: In the Usage Notes or Roadmap Considerations section, consider adding a point about adapting the level of detail to the scope of the request. For example: "The level of detail in the roadmap should be proportional to the complexity of the request. A roadmap for a single feature may be simpler than a roadmap for an entire system migration." This would guide the AI to be more flexible.

2. Generalize Timeline Examples: In the Roadmap Phases example, you could make the timeframes more generic to encourage the AI to infer them from the context.

   • Current: ### Phase 1: Foundation (Months 1-3)
   • Suggestion: ### Phase 1: Foundation (Approx. Q1 / Months 1-3) or ### Phase 1: Foundation [Timeframe: 3 Months]
     This small change signals that the timeframe is a variable to be determined.

3. Minor Polish on ASCII Timeline: The ASCII art for the timeline is a great touch. The final horizontal line in the Phase 3 row extends slightly past the right vertical bar. This is a tiny cosmetic nitpick, but adjusting it would provide a bit more polish.

   // Current
   ├── Phase 3 ────────────────┤
   // Suggestion
   ├── Phase 3 ───────────────┤
   

---

Review of Specific Areas

• Code quality and best practices: Excellent. The markdown is clean, well-structured, and follows best practices for defining AI commands by providing clear instructions, examples, and context handling.
• Security concerns: None. The PR adds documentation and does not introduce any security risks.
• Performance implications: None. This is a documentation change and has no direct performance impact on any system.
• Test coverage: The PR author states that all relevant local tests (validation, linting, pre-commit) have passed, which is sufficient for a change of this nature.
• Documentation updates needed: The PR is the documentation update, and it correctly modifies all necessary files. No further documentation is needed.

---

Overall Recommendation

Approve

This is a high-quality contribution that adds significant value. It introduces a powerful and well-defined command that fills a clear need in the workflow command suite. The author has demonstrated a deep understanding of both strategic planning and how to effectively instruct an AI model.

The suggested improvements are minor and can be considered for future refinement. The PR is ready to be merged as is. Great work

---

This review was automatically generated by google/gemini-2.5-pro via OpenRouter. Please consider it as supplementary feedback alongside human review.

[github-actions]

🎉 This PR is included in version 1.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀