What is the purpose of the "Execution Flow" and similar sections in rendered spec.md and plan.md?

[smackesey]

templates/spec.md and templates/plan.md both have "Execution Flow" sections at the top.

As best I can tell, these are a guide for how to fill out the rest of the document-- so why are they included in the rendered spec.md/plan.md files? They only seem to interfere with human readability. It seems like the part intended for human consumption in spec.md starts at User Scenarios and Testing, and for plan.md starts at Phase 0.

[airtonix]

It seems like a creative use of context poisoning.

Its contextual guidance for the LLM to follow.

These files just end up as part of the context in your chat sessions. so having these sections helps enforce some alignment.

Agree that these sections might benefit from something like :

> [!NOTE]
> Following 'Execution Flow' is for context alignment and not indended for human consumption.

Note

Following 'Execution Flow' is for context alignment and not indended for human consumption.

I'm not sure they can be abstracted because they often end up having content specific to the spec you're working on.

[smackesey]

Since I posted this question, they've been removed from the templates (the equivalent now lives in the commands themselves)