Llm Process Domain Expert

To structure reusable LLM processes across multiple host repositories, you separate host project state under .spipe/<feature>/ from shared assets under .spipe/spipe/, linking documentation into doc/00_llm_process/ through setup scripts to maintain consistency.

The best way to link documentation directories safely is using setup-script-driven linking rather than manual copying, applying platform-appropriate mechanisms like symlinks versus Windows junctions to ensure repository layout consistency across operating systems.

You organize expert directories and skill layouts by standardizing ownership boundaries that define how command surfaces, SPipe tests, and process assets are structured, ensuring repeatable reuse across templates.

Yes, this LLM process design approach works for SPipe testing and loop documentation by applying standardized layout authoring and ownership boundaries to keep multi-repo templates consistent and maintainable.

Setup scripts are used instead of manual copy for documentation linking because they automate platform-specific symlink versus junction creation, preventing broken links and keeping repository layouts maintainable across host environments.