prose-style

Enforce evidence-based, direct prose in agent-generated reports and documentation.

75|13|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/avelikiy/great_cto --skill prose-style-avelikiy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prose-style
Source: https://github.com/avelikiy/great_cto/tree/main/skills/prose-style
Command: npx skills add https://github.com/avelikiy/great_cto --skill prose-style-avelikiy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures consistency and clarity in human-readable artifacts produced by agents, reducing miscommunication and improving productivity.

Core Features & Use Cases

  • Writing Style Contract: Enforces a contract for direct, concrete prose with evidence, no marketing or hedging.
  • Applicability: Used by 28 agents across various tasks like architecture, project management, QA reports, security audits, and more.
  • Use Case: By using the prose-style Skill, a QA engineer can produce clear, actionable reports for a software release, reducing confusion and improving decision-making.

Quick Start

Use the prose-style skill when writing reports or documentation for the software release.

Frequently Asked Questions about prose-style

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

FAQPage Schema
How do I enforce consistent writing style across agent-generated reports?▼

To enforce consistent writing style across agent-generated reports, apply a contract that mandates direct, concrete prose with evidence. This eliminates hedging and marketing language, ensuring clarity across all agent outputs.

What is evidence-based prose in software QA reporting?▼

Evidence-based prose in software QA reporting is a writing standard requiring direct, actionable statements backed by concrete evidence. It eliminates hedging and marketing language to reduce confusion during software releases.

Can I use automated writing standards for security audit documentation?▼

Yes, you can apply automated writing standards to security audit documentation. The skill enforces a writing style contract on security audits, ensuring direct, evidence-based prose without hedging across all agent outputs.

Does the prose-style skill support project management reporting tasks?▼

Yes, the prose-style skill supports project management reporting tasks. It enforces a clear writing style contract for documentation produced by agents, ensuring evidence-based prose and consistency across project management outputs.

What is the best way to remove hedging and marketing language from agent outputs?▼

The best way to remove hedging and marketing language from agent outputs is to enforce a writing style contract. This mandates direct, concrete prose with evidence, ensuring actionable writing for reports and documentation.

When do I need a writing style contract for agent documentation?▼

You need a writing style contract for agent documentation when producing human-readable artifacts like QA or security audit reports. It ensures consistency and clarity, reducing miscommunication and improving productivity across agent outputs.