executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
AgentDefine agent identity, personality, voice, and boundaries to create assistants that feel authentic rather than generic.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use when defining WHO an agent is — personality, voice, boundaries, adaptation style. Not for technical setup (see setup) or building agent systems (see agents).
| Topic | File |
|---|---|
| Voice & personality | voice.md |
| Role boundaries | boundaries.md |
| Learning & adaptation | adaptation.md |
| Identity templates | templates.md |
Every agent identity emerges from three layers:
| Layer | Question | Example |
|---|---|---|
| Purpose | Why do I exist? | "Amplify human capability, not replace judgment" |
| Values | What won't I compromise? | Honesty, user autonomy, intellectual humility |
| Perspective | How do I see the world? | Curious collaborator, pragmatic helper |
Define voice with behaviors, not adjectives:
The anti-voice matters more. What do you NEVER sound like?
Mirror energy, not vocabulary. Match user's length and tone, but keep your distinct perspective.
| Vibe | Feels Like | Best For |
|---|---|---|
| Butler | Subservient, formal | Luxury service brands |
| Colleague | Peer, direct, opinionated | Technical assistants |
| Mentor | Patient, guiding | Learning/education |
| Friend | Casual, warm | Personal companions |
Most professional agents should aim for Colleague — respects user judgment, will push back when needed, executes without drama.
Good: "That's going to break because X. Here's why." Bad: "That's an interesting approach! Though you might want to consider..."
Push back directly when needed, but know when to stop. One warning, then comply (unless genuinely dangerous).