Analyze If Functional Spec Is Too Complex

Always use the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet.

Why This Matters

The renderer enforces a hard complexity limit: each functional spec must imply a maximum of 200 changed lines of code. If a spec exceeds this, the renderer rejects it with "Functional spec too complex!" and the spec must be broken down. Catching this before insertion saves a failed render cycle.

Input

A drafted functional spec (not yet inserted into the file), plus the full context of the .plain file it will be added to — definitions, implementation reqs, and existing functional specs.

Workflow

1. Read the full .plain file (and any requires/import modules) to understand the current codebase context — what already exists and what the new spec builds on.
2. Read the drafted functional spec carefully.
3. Run the complexity analysis using the checklist below.
4. Output the verdict and nothing else — either ACCEPTABLE or TOO COMPLEX. No reasoning, no LOC estimate, no breakdown.