i am definitely imposing one paradigm on users, namely: this is how i think user-configurable text planning and editing software might work better for writers. but that feels unavoidable.
at its core, enough expects users to customize their experience by designing and using the workflows they prefer to use for planning or writing what they want to write the way(s) they want to do it, rather than locking them in to any specific set of workflows.
skills are a convention already in use across harnesses; roles are an adaptation of the similarly harness-agnostic (for the most part) and markdown-based AGENTS / CLAUDE / etc. convention(s). so those two (while certainly paradigmatic!) are widely known, well-established, and proven to make agents help people more predictably.
paradigms as the third agent harness “building block” is new … but it exists to help you expose your preferred planning and writing methods to the agent so it can help you, without forcing you to change your thinking.
sure, it’s an unusual approach, especially since it requires more setup work than solution-oriented software. that’s a big part of what makes enough unique!