build-guide

A legal clinic practice guide configures student-facing workflows by capturing intake questions, red flags, refer-out criteria, and local rules for a specific practice area, storing the output as a markdown guide file.

A pedagogy posture in legal clinic configuration sets the teaching stance to assist, guide, or teach, establishing defaults and optional per-document overrides that shape how student-facing skills interact with clinic users.

Review gates and cross-plugin checks are established by defining which work products require supervising attorney review and recording which external-plugin skills students should use with applicable supervision wrappers in the practice guide.

Practice-area guide authoring requires supervising attorney access. The configuration process enforces supervisor-only access to ensure only authorized supervisors can write or revise clinic guide artifacts.

Generated practice guides are written to a deterministic guides/<practice-area>.md path, matching an expected template structure so downstream student-facing drafting and advising skills can read the configuration.

A clinic practice guide captures practice-area-specific local rules and forms pointers that downstream drafting and advising skills reference, ensuring jurisdiction-specific compliance during student work products.