build-guide

To create a practice-area configuration guide, you run a supervisor-gated authoring process that defines intake workflow, pedagogy posture, review gates, cross-plugin checks, and local rules, then writes the output to the prescribed filesystem path.

Pedagogy posture defines the instructional stance—assist, guide, or teach—that student-facing legal clinic skills adopt when processing intake and interacting with users during workflows.

Yes, you can revise existing practice-area guides section-by-section or overwrite them entirely by re-running the skill, keeping configuration updates quick and auditable for student workflows and supervision routing.

Yes, authoring a clinic configuration guide requires supervising-attorney authorization. The skill reads the supervisor role from the clinic's CLAUDE configuration and halts execution if the user lacks authorization.

Review gates establish mandatory supervision checkpoints in student workflows, while cross-plugin checks validate consistency across integrated clinic skills, ensuring processes align with local rules and supervisor-defined configurations.

You need per-practice-area behavior tuning when a legal clinic requires distinct intake questions, pedagogy posture, review gates, and local rules for different practice areas, ensuring repeatable and auditable student workflow configurations.