Christopher Clendening
96b7ff9766
- Create SECURITY.md to outline security policies and practices. - Establish WORKFLOW.md detailing the project lifecycle from planning to retrospective. - Introduce decision log structure in decisions/README.md for tracking architecture decisions. - Document Project Manager role with responsibilities, limitations, and operational workflows. - Implement templates for ADRs, bugs, meetings, projects, retrospectives, RFCs, roadmaps, and sprints. - Set up memory logs for architecture and company-wide lessons learned. - Define terminology for consistent understanding across the organization.
27 lines
866 B
Markdown
27 lines
866 B
Markdown
# Roadmap — <Project Name or Company>
|
|
|
|
**Owner:** CEO (company-level) or Project Manager (project-level)
|
|
**Last updated:** YYYY-MM-DD
|
|
|
|
A roadmap here is a snapshot for human/agent readability — Plane's Epics and milestones
|
|
(`PLANE.md`) remain the actual source of truth for priority and sequencing. If this file and
|
|
Plane disagree, Plane is right and this file is stale; update it.
|
|
|
|
## Now
|
|
|
|
Epics/Stories actively in progress this cycle. Link to Plane.
|
|
|
|
## Next
|
|
|
|
Approved (cleared the `FOUNDER.md` gate) but not yet started.
|
|
|
|
## Later
|
|
|
|
Directionally likely but not yet through the approval gate — clearly marked as such so no one
|
|
mistakes "later" for "approved."
|
|
|
|
## Explicitly out of scope
|
|
|
|
What this roadmap deliberately excludes, and why — as useful as what's in scope, especially for
|
|
preventing scope creep an engineer might otherwise assume is implied.
|