Added the Tech Content Editorial Board agentic workflow

[fnipo]

This PR introduces a new agentic workflow: Tech Content Editorial Board.

This was an idea I had inspired by repo-assist, but aimed more specifically at helping me improve the quality of the articles in my tech blog. Instead of acting like a broad repository assistant, this workflow behaves more like a small editorial board for technical writing: reviewing clarity, rigor, structure, caveats, and overall usefulness for engineering readers.

What it adds

• a new workflow focused on technical-content review
• a board-style simulation with multiple personas and viewpoints
• a bias toward small, focused content improvements
• tracking for broader editorial backlog when needed
• documentation for how the workflow works and what kind of output it produces

Notes

This is an initial version, and I expect it will improve with iteration. I am very open to feedback on the workflow design, the personas, the output format, and whether the scope feels right for technical blog content.

If anything feels too heavy, too broad, or not practical enough, I would really appreciate suggestions.

Examples

Issue: fnipo/fnipo.github.io#20
Pull request: fnipo/fnipo.github.io#19