Marat Zimnurov

You can maintain bilingual repository documentation, build evidence-backed master prompts for complex initiatives, produce ten-second OKR status briefs, design umbrella repositories coordinating component repos, write documentation portal articles and tool sections, and operate multi-agent units for long-running engineering work.

They target lead and senior full-stack engineers running cross-repository, spec-driven initiatives. Typical users maintain multilingual docs, coordinate concurrent agents on shared accounts, hand over long-running work via standups and status briefs, or repair documentation portal pages rejected as not written for humans.

Use state for 'where are we' questions: an OKR-shaped brief with one objective line, scored key results, the blocker, and the ask. Use write-post for documentation portal articles where conclusions and numbers appear on the first screen. Never use state when the answer is a single fact.

Use it when work must split across many concurrent agents, when a shared account makes write collisions likely, or when agents die in batches on session limits and must resume without re-deriving measurements. Skip it when one agent finishes the work in a single session.

You need a cross-repository initiative spanning multiple independently versioned component repositories. The skill covers pinned revisions, shared agent rules, spec-driven artifacts, general and component-specific skills, and an analyst workspace. Do not use it when one repository already owns the whole change.