TODO: Reassign Scattered Notes to AI Agency Project
Discovered 2026-03-01 during plan-2026-02-28-agent-skill-frontmatter Phase 4 prep.
Why This Matters
Claude Config is the technical enforcement layer — hooks, frontmatter, settings.json. It implements SOPs; it doesn't own them. SOPs, agent profiles, skill definitions, templates, and architecture docs are owned by AI Agency. They live in pal-e-docs.
Right now ~25 notes are filed under Claude Config or pal-e-docs simply because those projects existed first. This violates the ownership boundary:
- AI Agency owns the what — SOPs, agent profiles, skill definitions, templates, workflow architecture
- Claude Config owns the how — hooks, frontmatter, settings.json, the plumbing that enforces SOPs at runtime
- pal-e-docs owns the app — the knowledge system itself (schema, API, MCP, deployment, content conventions)
The boundary: if it's "what should happen" it belongs to AI Agency. If it's "how it's technically enforced" it belongs to Claude Config. If it's about the pal-e-docs application, it stays on pal-e-docs.
Notes to Reassign to AI Agency
Agent Profiles (currently: Claude Config)
| Slug |
Current Project |
Action |
| <code>agent-betty-sue</code> |
Claude Config |
Move to AI Agency |
| <code>agent-dev</code> |
Claude Config |
Move to AI Agency |
| <code>agent-qa</code> |
Claude Config |
Move to AI Agency |
| <code>agent-issue-creator</code> |
Claude Config |
Move to AI Agency |
Skills (currently: Claude Config)
| Slug |
Current Project |
Action |
| <code>skill-plan</code> |
Claude Config |
Move to AI Agency |
| <code>skill-review-pr</code> |
Claude Config |
Move to AI Agency |
| <code>skill-implement-phase</code> |
Claude Config |
Move to AI Agency |
| <code>skill-fix-review</code> |
Claude Config |
Move to AI Agency |
| <code>skill-create-issue</code> |
Claude Config |
Move to AI Agency |
Workflow SOPs (currently: Claude Config)
| Slug |
Current Project |
Action |
| <code>worktree-workflow</code> |
Claude Config |
Move to AI Agency |
| <code>pr-lifecycle</code> |
Claude Config |
Move to AI Agency |
| <code>pr-review-loop</code> |
Claude Config |
Move to AI Agency |
| <code>solo-dev-pr-workflow</code> |
Claude Config |
Move to AI Agency |
| <code>sop-index</code> |
Claude Config |
Move to AI Agency |
Workflow SOPs (currently: pal-e-docs)
| Slug |
Current Project |
Action |
| <code>agent-workflow</code> |
pal-e-docs |
Move to AI Agency |
| <code>agent-spawn-conventions</code> |
pal-e-docs |
Move to AI Agency |
Architecture Docs (currently: mixed)
| Slug |
Current Project |
Action |
| <code>enforcement-architecture</code> |
Claude Config |
Move to AI Agency |
| <code>hook-events-reference</code> |
Claude Config |
Move to AI Agency |
| <code>agent-paradigm</code> |
pal-e-docs |
Move to AI Agency |
Templates (currently: mixed)
| Slug |
Current Project |
Action |
| <code>template-agent</code> |
Claude Config |
Move to AI Agency |
| <code>template-skill</code> |
Claude Config |
Move to AI Agency |
| <code>template-plan</code> |
Claude Config |
Move to AI Agency |
| <code>template-pr-body</code> |
Claude Config |
Move to AI Agency |
| <code>template-issue</code> |
pal-e-docs |
Move to AI Agency |
| <code>template-project-page</code> |
(check) |
Move to AI Agency |
| <code>template-bug</code> |
(check) |
Move to AI Agency |
Notes that STAY where they are
| Slug |
Project |
Why |
| <code>sop-claude-config-development</code> |
Claude Config |
About developing the claude-custom repo specifically — the one SOP Claude Config owns |
| <code>sop-litestream-restore</code> |
pal-e-docs |
About the pal-e-docs app infrastructure |
| <code>note-conventions</code> |
pal-e-docs |
About pal-e-docs content formatting |
| <code>html-style-guide</code> |
pal-e-docs |
About pal-e-docs HTML conventions |
| <code>tagging-conventions</code> |
pal-e-docs |
About pal-e-docs taxonomy |
| <code>deployment-lessons</code> |
pal-e-services |
Platform infra knowledge |
| <code>service-onboarding-sop</code> |
pal-e-services |
Platform infra SOP |
| <code>namespace-conventions</code> |
pal-e-services |
K8s namespace convention |
Stale Agent Names to Fix (same pass)
While reassigning, also fix stale agent names in these notes:
| Note |
Stale Reference |
Replace With |
| <code>enforcement-architecture</code> |
"Devy", "Mandy" |
"Betty Sue" / "Dev Agent" / "QA Agent". Remove Mandy entirely (never existed). |
| <code>agent-paradigm</code> |
"Devy", "Mandy" |
Same replacements. Remove Mandy. |
| <code>agent-workflow</code> |
"Devy" |
"Betty Sue" |
| <code>pr-lifecycle</code> |
"Devy" (in mermaid diagram) |
"Betty Sue" or "Main Session" |
Execution
Non-destructive: update_note(slug="...", project_slug="ai-agency") for each note. Content edits for stale names done in the same pass. Approximately 25 notes to reassign, 4 notes need content edits.
plan-2026-02-28-agent-skill-frontmatter — Phase 4 references this TODOproject-ai-agency — the destination project (see Ownership Boundary section)project-claude-config — see "What This Project Does NOT Own" section