These are the raw, unedited notes I wrote while shaping this article. They are closer to a brain dump than a prompt library: my thinking, philosophy, corrections, and direction. The ideas are mine. AI helped turn them into a smoother, more readable essay.

Prompt 1
i want to write an engineering article with neat/tricky animation preamble for the 100 PRs of the /Users/goga/Documents/goga/backlog-mcp https://github.com/gkoreli/backlog-mcp

i am 117 PRs, and then at some point i moved to making commits and pushing directly, no more PRs, but those initial 100PRs were instrumental for this project. For example, in one of the weekends i created my own UI framework, because I was facing lots of challenges in the UI at that point, so i had no other choise, i ran a spike with react and didn't like it, and no other UI framework aligned with my vision. I want to write like an engineering article almost like research paper but mostly engineering challenges, ideas, and vision that i have for the future of agentic engineering, my thinking, mental model and so on, you will have to mine this information across PRs, project files, ADRs and so on... You can delegate to sub-agents, use Sonnet for exploration and mining information or any hard labor tasks that you have that don't require critical judgment like you as Fable 5 the most advanced model, you are the brain and main writer.
Prompt 2
write the .ts based advanced blog, you can have some cross references with rationale and why they matter relative to the article we are writing. Make sure to write a catchy engineering article. Be mindful about SEO so that people find out about us, about backlog mcp, about nisli/core ui framework and about me.
Prompt 3
Also you can start another exploration to figure out what it means to write like Goga and what it means to write catchy articles in present tense. read the my personal creative writing skill thats mutual for both of us .agents/skills/personal-essays/SKILL.md - respect it and the article needs to respect it as well
Prompt 4
i think the article is talking too much about the numbers as if its like analytics, the numbers are a consequence the article is about the saga, its like a part 1 of the backlog mcp as a product article series, but from the perspective of 100 PRs, what it means, what does it take to be building in open source as Goga, what does it mean to be so determined to be building from personal pain of not having proper task management tools and so on.