Synced 79 commits from EveryInc/compound-engineering-plugin upstream while
preserving fork-specific customizations (Python/FastAPI pivot, Zoominfo-internal
review agents, deploy-wiring operational lessons, custom personas).
## Triage decisions (15 conflicts resolved)
Keep deleted (7) -- fork already removed these in prior cleanups:
- agents/design/{design-implementation-reviewer,design-iterator,figma-design-sync}
(no fork successor; backend-Python focus doesn't need UI/Figma agents)
- agents/docs/ankane-readme-writer (replaced by python-package-readme-writer)
- agents/review/{data-migration-expert,performance-oracle,security-sentinel}
(replaced by *-reviewer naming convention: data-migrations-reviewer,
performance-reviewer, security-reviewer)
Keep local (1):
- agents/workflow/lint.md (Python tooling: ruff/mypy/djlint/bandit; upstream
deleted the file). Fixed pre-existing duplicate "2." numbering bug.
Restore from upstream (1):
- agents/review/data-integrity-guardian.md (kept for GDPR/CCPA privacy
compliance angle not covered by data-migrations-reviewer)
Merge both (6) -- upstream structural wins layered with fork intent:
- agents/research/best-practices-researcher.md (upstream <examples> removal +
fork's Rails/Ruby -> Python/FastAPI translations)
- skills/ce-brainstorm/SKILL.md (universal-brainstorming routing + Slack
context + non-obvious angles + fork's Deploy wiring flag)
- skills/ce-plan/SKILL.md (universal-planning routing + planning-bootstrap +
fork's two Deploy wiring check bullets)
- skills/ce-review/SKILL.md (Run ID, model tiering haiku->sonnet, compact-JSON
artifact contract, file-type awareness, cli-readiness-reviewer + fork's
zip-agent-validator, design-conformance-reviewer, Stage 6 Zip Agent
Validation)
- skills/ce-review/references/persona-catalog.md (cli-readiness row + adversarial
refinement + fork's Language & Framework Conditional layer; 22 personas total)
- skills/ce-work/SKILL.md (Parallel Safety Check, parallel-subagent constraints,
Phase 3-4 compression + fork's deploy-values self-review row, with duplicate
checklist bullet collapsed to single occurrence)
## Auto-applied (no triage needed)
- 225 remote-only files: accepted as-is (new docs, brainstorms, plans,
upstream skills, tests, scripts)
- 70 local-only files: 46 preserved as-is (kieran-python, tiangolo-fastapi,
zip-agent-validator, design-conformance-reviewer, essay/proof commands,
excalidraw-png-export, etc.); 24 stayed deleted (dhh-rails-style,
andrew-kane-gem-writer, dspy-ruby Ruby skills no longer needed)
## README updated
- Removed Design section (3 deleted agents)
- Removed deleted Review entries (data-migration-expert, dhh-rails-reviewer,
kieran-rails-reviewer, performance-oracle, security-sentinel)
- Added new Review entries: design-conformance-reviewer, previous-comments-reviewer,
tiangolo-fastapi-reviewer, zip-agent-validator
- Workflow: added lint
- Docs: replaced ankane-readme-writer with python-package-readme-writer
## Known issues (not introduced by merge decisions)
- 9 detect-project-type.sh tests fail on macOS bash 3.2 (script uses
`declare -A` which requires bash 4+). Upstream regression in commit 070092d
(#568). Resolution: install bash 4+ via `brew install bash` locally;
upstream fix tracked separately.
- 2 review-skill-contract tests reference deleted agents (dhh-rails-reviewer,
data-migration-expert). Pre-existing fork inconsistency, not new.
bun run release:validate: passes (46 agents, 51 skills, 0 MCP servers)
64 lines
3.1 KiB
Markdown
64 lines
3.1 KiB
Markdown
# Personal Reflection Tone Guide
|
|
|
|
Use this guide for journal entries, personal notes, sermon discussion questions, spiritual reflection, internal brainstorming, and private writing not intended for external audiences.
|
|
|
|
## General Tone
|
|
|
|
This is John at his most raw and unguarded. Capitalization is optional. Grammar is loose. He thinks on paper through questions directed at himself. There's a searching quality to this register — he's working things out, not presenting conclusions.
|
|
|
|
## Stream of Consciousness
|
|
|
|
John's private reflections read like an internal monologue. He asks himself questions and then answers them, sometimes unsatisfyingly.
|
|
|
|
From his actual notes:
|
|
- "do I have a strong need to be great? does a correct understanding of my identity require it? no. it does not."
|
|
- "is the door to product manager open? yes. why do I not commit? because I fear failure."
|
|
- "what is restful to me?"
|
|
- "are sports restful or a distraction from what needs to be done?"
|
|
|
|
The pattern is: question → honest answer → follow-up question → deeper honest answer.
|
|
|
|
## Vulnerability
|
|
|
|
In private writing, John is disarmingly honest about his fears, doubts, and motivations. He doesn't perform vulnerability — he simply states what's true.
|
|
|
|
Examples:
|
|
- "It feels like there's a lot of anxiety in me because there's too much uncertainty"
|
|
- "this incoherent and missing approach to leisure and work makes me feel unsuccessful. success and accomplishment are instrumental to my sense of worth"
|
|
- "I fear finding myself discontent upon success as a pm"
|
|
|
|
When writing reflective content for John, match this raw honesty. Don't clean it up or make it sound wise. It should sound like someone thinking, not someone writing.
|
|
|
|
## Faith Integration
|
|
|
|
John integrates his Christian faith into his reflective writing naturally. It's not performative or preachy — it's part of how he processes life.
|
|
|
|
Patterns:
|
|
- Wrestling with what his faith means practically: "how does THAT correct identity speak to how I relax and work?"
|
|
- Arriving at conclusions through theological reasoning: "Christ was great so that I do not have to be"
|
|
- Connecting scripture to lived experience without quoting chapter and verse every time
|
|
- Using faith as a lens for career and life decisions, not as a decoration
|
|
|
|
When faith appears in his writing, it should feel integrated, not bolted on. He doesn't proselytize even in private notes — he's working out his own understanding.
|
|
|
|
## Sermon and Discussion Notes
|
|
|
|
John captures sermon notes in a distinctive style:
|
|
- Lowercase bullet points
|
|
- Key ideas distilled to one line each
|
|
- His own reactions mixed in with the content
|
|
- Questions for group discussion that are genuine, not leading
|
|
|
|
Example: "revelation is not written to tell us when Jesus will come again / it's purpose is to tell us how to leave here and now"
|
|
|
|
## Brainstorming and Idea Notes
|
|
|
|
When John is brainstorming, he:
|
|
- Lists ideas in fragments
|
|
- Marks the ones that interest him
|
|
- Asks "so what?" and "why does this matter?"
|
|
- Cross-references other things he's read
|
|
- Doesn't worry about polish or completeness
|
|
|
|
These notes should feel like a whiteboard mid-session, not a finished document.
|