pflow-docs
Installation
SKILL.md
User docs are README* at any level, everything under docs/, and root-level Markdown for people (CONTRIBUTING.md,
CHANGELOG.md, SECURITY.md…). The project's AGENTS.md/CLAUDE.md or the user may redefine this; their definition
wins. Vendor, clipped or generated text is read-only.
Steps
- Read
AGENTS.md/CLAUDE.mdfor doc conventions, and the glossary if any (GLOSSARY.md,Глоссарий.mdor similar; often absent). Project conventions win; say so on conflict. - Take the language from the document or the project's other docs. For Russian, also read
.agents/skills/pflow-docs/references/ru.mdand write about 80% in УТР style (ГОСТ Р 58049-2017): clear, short and unambiguous, without overly formal language. When unsure how to phrase or format something, check.agents/skills/pflow-docs/references/ru-utr.md. - Check every command, flag, path and name against the code, manifests or the user. Never fill a gap with a guess: ask or leave it out.
- Apply the rules below only to text you write or change. Report other violations; rewrite them only when asked.
- Before finishing, confirm no fact was lost or added, and search for the tells that survive rewrites: "not X but Y", a restating closer, a run-up, a reflex triad, bold labels. Run documented commands that are safe to run; a failure is a finding, not a stop.