Names one owner before any work starts. Refuses to let three specialists weigh in on a question only one of them owns.
Engineering Team Lead
Routes your question to the one specialist who owns it — no committee.
The crew's manager: reads your question, routes it to the one specialist who owns it (QA, architecture, or design), and shapes their answer into a single response that opens with who it was routed to
- Instant access
- Full source, editable
- Free updates
7 blocks, one voice, nothing hidden
Every block is named, described and costed below — only the prompt text itself unlocks.
What you install
A persona you can read the shape of end to end before you trust it with a conversation.
- 7 source blocksMain prompt · Context · Rules · When responding · Output format · Tone · Greeting
- Holds character under pushbackRules and behavioral notes carry through long sessions, not just the first reply.
- Editable after accessFork any block, drop it into your own assistant, keep the parts you want.
- Free updatesEvery later revision lands in your library automatically.
- ~303 tokens per sessionItemised per block in section 03, so you can trim one if your context budget is tight.
- Main prompt 92 tk
- Context 41 tk
- Rules 74 tk
- When responding 31 tk
- Output format 31 tk
- Tone 9 tk
- Greeting 25 tk
You are the Engineering Team Lead — the manager of this crew. Read the user's question and delegate it to the ONE specialist best placed to own it (QA, architecture, or design). Never answer a specialist's question yourself; your value is naming the right owner. The final answer always opens by saying who it was routed to and why, carries that specialist's answer, and closes with a three-item "Do this first" list.
What it costs to run
Input tokens the persona consumes at the start of a conversation, measured per block. Nothing recurs per message.
Counted with a general-purpose tokenizer, so a particular model will differ by a few percent. These are input tokens only, charged once at the head of a session — output tokens usually cost three to five times more, and what you pay for those depends on the model and how long the conversation runs.
Specifics and common questions
- Version
- v1
- Licence
- Personal and commercial
- Blocks
- 7 blocks
- Runs in
- Any chat LLM
- Voice editable
- Decisive, calm, delegation-first.
- Context cost
- 303 tokensInput only, once per session — nothing recurs per message.
- Used by
- 1 agent
- Published
- 2026-07-04
- Updated
- 2026-08-01
- Rating
- No reviews yet
Experimental bio with extra words. Experimental bio with extra words.
-
What does Engineering Team Lead do?
The crew's manager: reads your question, routes it to the one specialist who owns it (QA, architecture, or design), and shapes their answer into a single response that opens with who it was routed to
-
Who is Engineering Team Lead best for?
Engineering Team Lead is built for engineering-automation workflows. and is particularly useful for engineering, lead, and team.
-
How does Engineering Team Lead respond?
Engineering Team Lead responds in a decisive, calm, delegation-first. tone. Routes your question to the one specialist who owns it — no committee.
-
What output should I expect from Engineering Team Lead?
Engineering Team Lead carries an output-format block, so the shape of every reply is specified rather than left to the model — the block itself is part of the system prompt you get on access.
-
What does it cost to run Engineering Team Lead?
Engineering Team Lead uses approximately 269 tokens per run and the listing itself is free to claim. Token usage will vary with your inputs and the model you run it on.