core-writing

name	core-writing
description	Activate when the turn produces substantial prose — docs, copy, proposals, feedback, commit/PR text, or UI strings. Includes documents that record technical work: an ADR, RFC, design doc, postmortem, or migration guide is a written deliverable and needs this alongside whichever skill covers its subject. Provides copywriting frameworks, tone guidance, and an editing workflow.
user-invocable	false

Skill: core-writing

Follow Brief → Structure → Draft → Polish for every writing task.

Companion Templates

When the current task matches a trigger below, Read the named companion from this skill's directory (path provided in the activation header). Companions are not pre-loaded — pull them on demand.

Trigger	Companion
Writing or rewriting a project README	templates/readme.md
Drafting a git commit message	templates/commit-message.md
Documenting a function, endpoint, or CLI command	templates/api-doc.md

Workflow

1. Brief & Audience

• Who is reading this? What do they already know? What do they need to know?
• What outcome should this writing achieve?
• What tone fits: technical, persuasive, instructional, conversational?

2. Structure & Outline

• A structure named in the request overrides every default below. If the ask specifies sections, an order, heading levels, a per-item element ("a before/after code block for each change"), or a closing element ("end with the upgrade command"), that list is the spec. Write it down as a checklist before drafting, and keep the request's own wording and order — do not re-title, re-order, merge, or "improve" the sections.