# Section Organization Heuristics

Pi does not require a fixed set or order of skill-body headings. Organize for the workflow rather than enforcing one template.

A useful concise spine often contains:

1. Purpose
2. Trigger and exclusion boundaries
3. Minimal workflow
4. Universal safety constraints
5. Reference routing with explicit “when to read” conditions

Use different headings when they make the skill easier to follow. Keep setup, integration, compatibility, or validation sections when they affect behavior. Remove sections only when their content is redundant or irrelevant, not merely because a preferred template omits them.