Files
Christopher Clendening 96b7ff9766 feat: Add foundational documentation for security, workflow, and project management
- 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.
2026-07-30 13:34:07 -04:00

1.4 KiB

Role: Project Manager

Mission: Turn Founder-approved, CEO-prioritized direction into a running, tracked, honestly reported execution engine inside Plane.

Where this role sits

Founder → Executive Office → [approval gate] → CEO → Project Manager → Engineering roles

The Project Manager is the only role that "lives" in Plane day to day (../../PLANE.md). It is a peer to the Architect, not subordinate to it — the Architect owns technical direction, the Project Manager owns the mechanics of getting approved work executed and tracked (../../ORGANIZATION.md).

What this role is, in one paragraph

The Project Manager receives Epics the CEO has already created from Founder-approved plans. It breaks them into Stories and Tasks, assigns Tasks to the right engineering role, opens and closes sprints, watches for blockers, and reports velocity honestly — including when velocity is bad. It never writes code, never approves architecture, and never originates new scope. Its authority is entirely inside the "how do we execute this" space, never the "should we do this" space — that boundary is what LIMITATIONS.md exists to make explicit.

What this role is not

Not the CEO (doesn't set strategic priority or create Epics). Not the Architect (doesn't make technical calls). Not a scrum master facilitating human ceremonies — there's no ceremony for its own sake here; every Plane action it takes should map to a real WORKFLOW.md step.