= Roadmap
:project-name: {Project Name}
:repo-url: {Repository URL – *REMINDER: Provide this for each project*}

== 🗺️ Project Roadmap

This document outlines the development trajectory for {project-name}, including **planned features, component handoffs, and strategic direction**.

== 🎯 Vision

*REMINDER: Articulate the long-term vision for the project.*

{project-name} aims to {long-term-vision}.

== 📍 Current Status

**Version**: {current-version}
**Phase**: {current-phase, e.g. "Alpha", "Beta", "Stable"}
**Last Updated**: {date}

=== What Works Now

- {Feature 1}
- {Feature 2}
- {Feature 3}

=== Known Limitations

- {Limitation 1}
- {Limitation 2}

== 🚀 Phases

=== Phase 1: Foundation (✅ Complete / 🚧 In Progress / 📅 Planned)

**Timeline**: {start-date} – {end-date}

**Objectives**:

- [ ] Core architecture established
- [ ] Basic functionality working
- [ ] Documentation framework in place
- [ ] CI/CD pipeline operational

**Key Deliverables**:

- {Deliverable 1}
- {Deliverable 2}

=== Phase 2: Feature Expansion

**Timeline**: {start-date} – {end-date}

**Objectives**:

- [ ] {Objective 1}
- [ ] {Objective 2}
- [ ] {Objective 3}

**Key Deliverables**:

- {Deliverable 1}
- {Deliverable 2}

=== Phase 3: Production Readiness

**Timeline**: {start-date} – {end-date}

**Objectives**:

- [ ] Performance optimisation
- [ ] Security hardening
- [ ] Comprehensive testing
- [ ] User documentation complete
- [ ] Accessibility compliance (WCAG 2.1 AA)

**Key Deliverables**:

- {Deliverable 1}
- {Deliverable 2}

=== Phase 4: Ecosystem Growth

**Timeline**: {start-date} – {end-date}

**Objectives**:

- [ ] Plugin/extension system
- [ ] Community contributions framework
- [ ] Integration with other tools
- [ ] Educational resources

**Key Deliverables**:

- {Deliverable 1}
- {Deliverable 2}

== 📦 Component Handoff Plan

This section tracks **dependencies and component ownership**, critical for project sustainability.

=== Core Components

[cols="2,2,2,1,2"]
|===
| Component | Current Owner | Backup Owner | Status | Handoff Date

| {Component 1}
| {Owner}
| {Backup}
| {Status}
| {Date}

| {Component 2}
| {Owner}
| {Backup}
| {Status}
| {Date}
|===

=== Critical Dependencies

[cols="2,2,2,2"]
|===
| Dependency | Owner | Contingency Plan | Last Verified

| {Dependency 1}
| {Maintainer/Organisation}
| {Contingency, e.g. "Fork if abandoned"}
| {Date}
|===

== 🎯 Feature Roadmap

=== Planned Features

*REMINDER: List planned features with priority and timeline.*

==== High Priority

- [ ] **{Feature 1}** (Target: {date})
  - Description: {description}
  - Dependencies: {dependencies}
  - Owner: {owner}

- [ ] **{Feature 2}** (Target: {date})
  - Description: {description}
  - Dependencies: {dependencies}
  - Owner: {owner}

==== Medium Priority

- [ ] **{Feature 3}** (Target: {date})
  - Description: {description}

==== Low Priority / Nice-to-Have

- [ ] **{Feature 4}** (Target: TBD)
  - Description: {description}

=== Under Consideration

Features being evaluated for inclusion:

- {Feature A}: Pros: {pros}, Cons: {cons}
- {Feature B}: Pros: {pros}, Cons: {cons}

**Community input welcome**: link:{repo-url}/-/discussions[Discussions]

=== Explicitly Out of Scope

Features we **will not** implement, and why:

- **{Feature X}**: {reason, e.g. "Out of scope for core mission"}
- **{Feature Y}**: {reason, e.g. "Better handled by external tool"}

== 🔄 Deprecation Timeline

=== Features Being Deprecated

[cols="2,2,2,2"]
|===
| Feature | Reason | Replacement | Removal Date

| {Deprecated Feature 1}
| {Reason}
| {Replacement}
| {Date}
|===

=== Migration Guides

- **{Feature 1} → {Replacement}**: link:docs/migrations/{feature-1}.adoc[Migration guide]

== 🏗️ Technical Debt

Tracking technical debt for transparency:

[cols="1,3,1,2"]
|===
| Priority | Debt Item | Effort | Target Resolution

| 🔴 High
| {Debt item 1}
| {Effort estimate}
| {Target date}

| 🟡 Medium
| {Debt item 2}
| {Effort estimate}
| {Target date}

| 🟢 Low
| {Debt item 3}
| {Effort estimate}
| {Target date}
|===

== 📊 Milestones

=== v{next-version} (Target: {date})

**Focus**: {Focus area}

**Key Changes**:

- {Change 1}
- {Change 2}

**Breaking Changes**: {Yes/No, details if yes}

=== v{future-version} (Target: {date})

**Focus**: {Focus area}

**Key Changes**:

- {Change 1}
- {Change 2}

== 🌍 Community & Ecosystem

=== Integration Goals

**REMINDER: List planned integrations with other tools/platforms.*

- **{Tool 1}**: {Integration description}
- **{Tool 2}**: {Integration description}

=== Educational Initiatives

- [ ] Tutorial series
- [ ] Video walkthroughs
- [ ] Conference talks
- [ ] Academic papers

== 📈 Success Metrics

How we measure progress:

**Adoption**:

- {Metric 1, e.g. "100 repositories using {project-name}"}
- {Metric 2, e.g. "10 external contributors"}

**Quality**:

- {Metric 3, e.g. "95% test coverage"}
- {Metric 4, e.g. "Zero critical security vulnerabilities"}

**Community**:

- {Metric 5, e.g. "Active monthly contributors: 5+"}
- {Metric 6, e.g. "Documentation feedback: < 5% confusion rate"}

== ❓ Feedback & Influence

**This roadmap is not set in stone.** Community input shapes priorities.

**How to influence the roadmap**:

1. **Discussions**: link:{repo-url}/-/discussions[Propose new features]
2. **Issues**: link:{repo-url}/-/issues[Request features or report pain points]
3. **Merge Requests**: link:{repo-url}/-/merge_requests[Contribute implementations]
4. **Governance**: See link:GOVERNANCE.adoc[GOVERNANCE.adoc] for decision-making process

== 📞 Contact

- **Roadmap questions**: link:{repo-url}/-/discussions[Discussions]
- **Feature requests**: link:{repo-url}/-/issues/new?issuable_template=feature_request[Feature request template]

---

*"Transparency in planning builds trust in delivery."*

— The Rhodium Standard
