writing-skills

1# Writing Skills
2 
3## Purpose
4 
5Create the smallest reusable skill that changes decisions or improves task
6execution without constraining unrelated work. Skill changes use behavior
7validation, not a code TDD route. This validation does not require loading `aegis:test-driven-development`.
8 
9## Default Path
10 
11### 1. Establish Need And Ownership
12 
13- Name the reusable behavior gap, intended users/hosts, and non-goals.
14- Check whether an existing skill, project rule, host adapter, or automated
15  check already owns it. Prefer the smallest existing owner.
16- For an existing skill, inspect its references, manifests or generated copies,
17  discovery tests, and bundled resources before changing or retiring them.
18- Create a skill only for reusable, non-obvious guidance. Keep one-off project
19  conventions in the project owner and automate mechanical constraints when
20  practical.
21 
22### 2. Record Behavior Before Editing
23 
24Use representative tasks, not questions that merely ask the agent to recite
25instructions.
26 
27- New skill: run a no-skill control.
28- For an existing skill, run the current version first; add a no-skill ablation
29  only when testing whether the skill itself needs to exist.
30- Cover positive triggers, negative near-misses, and a pressure or application
31  case appropriate to the skill type.
32- Record decisions, missed or extra invocations, unsafe workarounds, evidence
33  references, and unknowns. Do not treat line or byte counts as behavior proof.
34…