writing

Enforce six writing rules for technical prose in agent-workflow outputs.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill writing-tacuchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing
Source: https://github.com/Tacuchi/agent-workflow-cli/tree/main/skills/w/roles/writing
Command: npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill writing-tacuchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear technical writing capability — built-in default for the writing role. Rules for any prose the AI produces in agent-workflow context: spec/plan/session artifacts, commit messages, PR descriptions, export deliverables (manuals/reports). Short sentences, lists over prose, one idea per line, what + why on one line, no jargon, no filler. Use across all loops and in export-manals / export-reports.

Core Features & Use Cases

  • Defines a disciplined, rule-based style for all AI-generated prose across specs, plans, artifacts, commits, and exports.
  • Guides export writing for manuals and reports with consistent readability.

Quick Start

Rewrite the provided text to comply with the six writing rules.

Frequently Asked Questions about writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce clear and concise technical writing in AI-generated prose?

To enforce clear technical writing, apply six rules: use short sentences, prefer lists over prose, keep one idea per line, state what and why on one line, and avoid jargon and filler across all AI outputs.

What is the best way to format commit messages and PR descriptions for readability?

The best way to format commit messages and PR descriptions is using disciplined technical writing rules, ensuring short sentences, bulleted structure, and clear what-and-why statements to maximize readability.

How do I write session artifacts and specs without unnecessary jargon?

To write session artifacts and specs without jargon, apply rule-based style constraints that enforce one idea per line, eliminate filler, and use bullet-friendly structure to maintain clear documentation.

Can I use these writing rules for export documents like manuals and reports?

Yes, you can use these writing rules for export documents like manuals and reports, as the style constraints are designed to guide consistent readability across all generated deliverables.

Does this approach work for formatting agent-workflow plans and specifications?

Yes, this approach works for formatting agent-workflow plans and specifications by providing a built-in default writing role that enforces concise, structured prose across all session artifacts.