joao-aires/documentation
Product and engineering writing, architecture explanation, knowledge upkeep and prose editing.
Explain and maintain a software system's architecture through structural views, runtime and lifecycle scenarios, interface analysis, deployment boundaries and evidence. Use for architecture documentation, system breakdowns and technical architecture reviews; preserve current versus target design and existing project scope.
Organize application knowledge and update affected PRDs, architecture, schemas, plans, decisions and runbooks when implementation or accepted decisions change. Use during planning, feature changes, migrations, deployment changes or documentation reviews.
Write and review clear, accurate, useful product and engineering documentation, including PRDs, requirements, architecture, decisions, feature specifications and operational guides. Use for new documents and substantive documentation revisions, adapting explanations, examples and presentation to readers.
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler. Based on Wikipedia's "Signs of AI writing."