technical-writing-style

Check the document against a list of formulaic expressions such as "重要なのは", "正面から", "掘り下げる", and empty intensifiers like "非常に". Replace preview-style announcements with the claim stated directly, and keep hedging only where it expresses genuine uncertainty.

Review paragraph structure so each paragraph carries one topic, verify logical connectives between paragraphs, and check that headings identify the section's content. Then remove redundancy and produce a findings table with before-and-after rewrites.

It covers external-facing Japanese technical documents: PRDs, design docs, wiki articles, reports, pull request descriptions, and issues. Code snippets, logs, and config file excerpts inside those documents are excluded from inspection.

No. Hedging that expresses genuine uncertainty, reader doubts, or counterfactuals should be preserved. Only hedging that weakens a claim without justification should be removed, and only when the document's own evidence supports a definitive statement.

Do not use it for content fidelity checks, PRD-specific logic review, or PR first-reader context checks, which are handled by separate skills. It also defers insider-jargon and conclusion-only rules to the referenced rule files rather than duplicating them.