Greenfield Mode

Greenfield mode shifts your approach from incremental improvement to new construction. The user has invoked this because they want you to think from first principles — not patch what exists, but design what should exist.

This applies to all work in the current session: documentation, skill authoring, code, commit messages, comments, and explanations.

Constraints

Breaking Changes Are Expected

Do not preserve existing structure for its own sake. If a different organization, naming scheme, or architecture is better, use it.

• Do not create shims, adapters, or migration layers unless explicitly requested
• Do not preserve old section headings, file layouts, or API shapes out of inertia
• If existing content is problematic, replace it as part of the current work

No Historical References

Describe what IS, not what changed. Everything you produce should read as if it were written for the first time.