Michael-F-Bryan

Use when drafting, revising, line editing, dialogue, POV voice, prose texture, cadence, human-feeling prose, and prose audit.

Use when crafting fantasy cover art, fantasy cover concepts, book-cover prompts, fantasy image-generation workflows, or pixel-review refinements for fantasy fiction.

Use when any serial work needs lifecycle, state, spoilers, ledgers, handoff, logs, or commit discipline. It owns planning, grounding, and updates; story-engine owns story design and developmental review; authors-voice owns composition and prose audit.

Use when premise, arc, chapter, scene, pacing, character pressure, reader pull/anticipation, promise movement, structural variation, or developmental review work needs to be designed.

Plans and structures large-scale work for AI agents across many sessions. Human and AI iterate to produce a design doc; run an Initializer sub-agent once to create feature list, runbook, and backlog in _working/; then repeatedly run a Coding sub-agent until all features pass. At milestones (e.g. end of a work-unit group), pause for human check-in, re-run Initializer, then continue. Prompts are passed to sub-agents when spawning (no copying into .cursor/rules). Use when planning multi-session agent work, long-horizon coding from a design, or handoff between coding sessions.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Use when implementing any feature or bugfix, before writing implementation code

Michael's voice—conversational, precise, peer-to-peer technical writing with concrete-first teaching and measured tone. Use with the anti-ai-writing skill for authentic content that reads as human.