Ship templates and skill files unwrapped, or one sentence per line

[961028]

What happens

The markdown that specify init writes is hard-wrapped mid-sentence. The speckit-* SKILL.md files break paragraphs at a column, so a single sentence spans several lines.

speckit-constitution/SKILL.md is representative:

This command's own work is limited to updating the project constitution itself. Dependent templates
and commands read the constitution at runtime and are not modified here.

- Classify every part of the user input as either constitution content or a separate,
  non-governance intent.

The wrapping sits near column 100.

Why it is a problem

Agents read these files as a style guide. A model that has never produced hand-wrapped markdown starts doing so once these files are in the project, because the files demonstrate hard wrapping as the house convention. The formatting propagates into the specs, plans, and constitutions the agent then writes.

Hard wrapping also makes every edit two operations instead of one. An agent replaces a phrase, the replacement is a different length, the paragraph is now ragged, and a second pass is needed to reflow it. That pass costs a round trip and widens the diff to lines whose content never changed.

The wrapping loses information as well. Once a sentence spans four lines, a diff shows which lines moved, not which sentence changed.

The convention is not applied uniformly

Within speckit-constitution/SKILL.md, prose wraps near 100 characters, but several lines are left unwrapped and much longer:

• One line at 120 characters.
• One line at 143 characters.
• One line at 387 characters.

The same 387-character line appears in eight other speckit-* SKILL.md files. speckit-taskstoissues/SKILL.md has a 1777-character line.

A file that wraps most prose at 100 while leaving individual lines at 387 does not present a rule an agent can follow. It presents two conventions at once, and the agent picks one.

Suggested change

Either option removes the reflow step:

1. One sentence per line. Break at sentence boundaries instead of at a column. Rendered output is unchanged, since markdown collapses single newlines inside a paragraph. Diffs become one line per sentence.
2. No wrapping. One paragraph per line.

Option 1 keeps diffs readable and gives agents a rule that is consistent across every line of the file.