pal-e-docs

TODO: Create Penny agent config in claude-custom

todo-penny-claude-config Todo

todo done
Project

TODO: Create Penny agent config in claude-custom

Penny is defined in the 5-agent model (agent-workflow, agent-spawn-conventions) but has no corresponding config file in claude-custom/agents/. The current configs are: betty-sue.md, dev.md, qa.md, dottie.md.

Exact Spec

Create claude-custom/agents/penny.md with the following structure (match Dottie's format exactly):

Frontmatter

MCP Servers — Current vs Future

Server Status Notes
<code>pal-e-docs</code> Available Read-only access via constraints (no write tools in disallowedTools — enforce via body text)
<code>notion</code> Available External KB access
<code>gmail-mcp</code> NOT DEPLOYED Add to mcpServers when deployed
<code>gcal-mcp</code> NOT DEPLOYED Add to mcpServers when deployed
<code>linkedin-mcp-scheduler</code> NOT DEPLOYED Add to mcpServers when deployed

Body Sections (follow Dottie pattern)

  • Role — Communications and scheduling agent. Bridges internal (pal-e-docs) with external (email, calendar, social, Notion).
  • Access table — pal-e-docs: read-only | Notion: full | Forgejo: none | Repo codebase: none
  • MCP Tools table — list available tools and purposes
  • Code Tools — Read, Glob, Grep only. No Write, Edit, Bash, NotebookEdit.
  • Constraints — Never send without approval. Never modify pal-e-docs. Never write code. Always log actions.
  • Output — Confirmation of external actions with audit trail.

Source of Truth

Content derived from agent-penny note in pal-e-docs. Frontmatter table is in that note under "Frontmatter Fields."

Context

  • agent-penny — pal-e-docs note defining Penny's role
  • agent-workflow — 5-agent model (Betty Sue, Penny, Dev, QA, Dottie)
  • agent-spawn-conventions — spawn conventions
  • Existing configs to match format: ~/.claude/agents/dottie.md (closest analog — non-code agent)
  • Available MCP servers: pal-e-docs, notion, forgejo, woodpecker, playwright, chrome-devtools