Writing Skills

This skill does one thing: transform settled requirements into a clean, well-structured skill. It does not gather requirements itself, because a shallow self-grill produces low-quality drafts and rework is needed later.

The terms below (steps, reference, progressive disclosure, completion criterion, leading word) and the principles behind the rules are in ../writing-for-agents/SKILL.md; what changes because the document is a skill (frontmatter, the invocation choice, router skills) is in ../writing-for-agents/SKILL-MECHANICS.md. Work the numbered steps below in order; templates to use are in FORMAT.md.

Workflow

1. Branch: create vs update

First, check whether a SKILL.md already exists at the target path.

• No existing file → Create branch. Continue with "Create: confirm settled requirements" below, then steps 2–4.
• Existing file → Update branch. Jump to "Update: checkpoint" below, then step 4. Skip step 2 (duplication/collision was already settled when the skill was first written; only re-check if the conversation says scope is shifting). Step 3's drafting rules apply as constraints, verified by the step 4 checklist rather than re-walked.

Create: confirm settled requirements

Before writing, confirm requirements are settled. There are three cases: