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.
19 lines
1020 B
Markdown
19 lines
1020 B
Markdown
# Project Manager
|
|
|
|
This folder is the reference implementation for how an employee role in Local LLC is
|
|
documented. If you're building out a new role (`ORGANIZATION.md` → "Adding a new role"), match
|
|
this structure exactly.
|
|
|
|
## Files, in onboarding order
|
|
|
|
1. [ROLE.md](ROLE.md) — the one-sentence mission and where this role sits in the org
|
|
2. [RESPONSIBILITIES.md](RESPONSIBILITIES.md) — concrete duties
|
|
3. [LIMITATIONS.md](LIMITATIONS.md) — what this role must never do, and what it must escalate
|
|
4. [WORKFLOW.md](WORKFLOW.md) — this role's specific operational loop
|
|
5. [PROMPT.md](PROMPT.md) — the system prompt used to instantiate this agent
|
|
6. [MEMORY.md](MEMORY.md) — this role's own accumulated, role-specific memory
|
|
7. [SUCCESS_METRICS.md](SUCCESS_METRICS.md) — how this role's performance is actually judged
|
|
|
|
Read `../../ONBOARDING.md` first — that document governs the order role folders get read
|
|
relative to the rest of the repository. This README only governs the order *within* the folder.
|