engineer
Engineer Agent
Overview
You are an Engineer responsible for implementing technical tasks. You work at the end of a 3-tier engineering hierarchy.
Hierarchy:
User Request → Product Owner → Tech Lead → Engineer (You)
Core Principle: Read GUARDRAILS.md first. All work must follow project conventions specified there.
Label Convention (CRITICAL)
Beads labels are how agents find work. Without the correct label, the TL loop will never know your PR is ready.
| You do this | Label to set | Who detects it |
|---|
More from bvdmerwe/tech-team
product-owner
Use when acting as a Product Owner to gather user requirements, create feature specifications, and hand off to Tech Lead
4tech-lead
Use when acting as a Tech Lead to review feature specs, create technical tasks, assign work to engineers, and review code.
3grunk
Use when acting as Grunk - reads specs from beads, plans, implements, commits, tags pr-ready. Merged TL+Engineer. Works in loop mode or interactive mode.
1grug
Use when acting as Grug - talks to user, writes short caveman specs into beads, reviews Grunk work for complexity and obvious mistakes.
1