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.
28 lines
733 B
Markdown
28 lines
733 B
Markdown
# Meeting — <topic>
|
|
|
|
**Date:** YYYY-MM-DD
|
|
**Attendees:** <roles/identities present>
|
|
**Related:** link to the Plane Epic/Story/Task this meeting concerns
|
|
|
|
## Purpose
|
|
|
|
Why this meeting happened — what decision or alignment it was for.
|
|
|
|
## Discussion
|
|
|
|
Key points raised, not a full transcript. Capture reasoning behind positions, especially where
|
|
there was disagreement (`EMPLOYEE_HANDBOOK.md` — disagreement should remain visible in the
|
|
record, not get smoothed over).
|
|
|
|
## Decisions made
|
|
|
|
- Decision — owner — any follow-up ADR needed? (`DECISIONS.md`)
|
|
|
|
## Action items
|
|
|
|
| Action | Owner | Due |
|
|
|---|---|---|
|
|
|
|
Link this file from the relevant Plane Epic/Story so it isn't disconnected from the work it's
|
|
about (`PLANE.md`).
|