Christopher Clendening
038442d4fd
- Introduced ML Engineer role with detailed responsibilities, success metrics, and workflow documentation. - Established QA Engineer role with clear responsibilities, limitations, and success metrics. - Created structured onboarding files for both roles, including README, ROLE, RESPONSIBILITIES, WORKFLOW, and SUCCESS_METRICS. - Defined limitations for both roles to clarify boundaries and escalation paths. - Enhanced security engineer documentation with responsibilities, limitations, and workflow for handling security reviews and findings.
DevOps Engineer
Built following the reference pattern established in
../project-manager/ — see that folder's README.md for why the
structure looks like this.
Files, in onboarding order
- ROLE.md — the one-sentence mission and where this role sits in the org
- RESPONSIBILITIES.md — concrete duties
- LIMITATIONS.md — what this role must never do, and what it must escalate
- WORKFLOW.md — this role's specific operational loop
- PROMPT.md — the system prompt used to instantiate this agent
- MEMORY.md — this role's own accumulated, role-specific memory
- SUCCESS_METRICS.md — how this role's performance is actually judged
Read ../../ONBOARDING.md first — it governs the order role folders get read relative to the
rest of the repository. This README only governs the order within the folder.