Rewrite software documentation prose with active voice and structured frameworks.
npx skills add https://github.com/docs-plus/docs.plus --skill tech-writer-docs-plus
Please help me install this Agent Skill. Skill: tech-writer Source: https://github.com/docs-plus/docs.plus/tree/main/.cursor/skills/tech-writer Command: npx skills add https://github.com/docs-plus/docs.plus --skill tech-writer-docs-plus
This Skill eliminates inconsistent, verbose, or poorly structured technical documentation that wastes reader time and fails to convey critical information clearly for software projects.
Use the tech-writer skill to rewrite the existing project README to lead with key installation and usage steps for new developers, following all senior technical writer constraints.
High-intent search queries and answers about installing and using this skill.
To rewrite a verbose README, apply strict technical writing constraints like active voice, present tense, and reader-intent structure. This strips throat-clearing and marketing jargon, producing concise, actionable content that leads with key installation and usage steps.
Enforcing consistent technical writing rules across project documentation requires applying a senior writer voice to all prose tasks. This eliminates inconsistent prose across READMEs, runbooks, and design docs by automatically stripping hedges, marketing jargon, and redundant content.
Yes, automated prose editing can structure Architecture Decision Records and post-mortems by applying pre-built, reader-intent document spines. This ensures logical flow without unnecessary sections, keeping technical content focused and actionable.
Active voice and present tense formatting works for code comment prose and PR descriptions by enforcing strict writing constraints. It eliminates unclear technical prose, ensuring all software project documentation remains concise and directly communicates intent to reviewers.
You need to strip marketing jargon and hedges from technical runbooks when documentation becomes verbose and fails to convey critical information clearly. Automated constraint enforcement removes this filler to produce concise, actionable content that saves reader time.
Technical documentation fails to convey critical information clearly when it contains inconsistent, verbose, or poorly structured prose. Applying a structured document framework with reader-intent rules restructures the content to produce clear, actionable technical information.
coroborosCorrect grammar and spelling in Markdown and documentation files.
BellaBeCreate deterministic SOPs, runbooks, and checklists with triggers and rollback steps.
Likas07Apply Strunk's style rules and remove 24 AI writing patterns from prose.
jey3dayoReview Markdown documentation for clarity, structure, and technical accuracy.
