teach-goal

Provide the target repository path and request a full walkthrough. The skill scans the repo, creates an L0 overview, builds a goal backlog of modules and features, then autonomously dispatches subagents to produce HTML lessons and reference docs until coverage checks pass.

A vertical slice traces one user-perceivable feature from its entry point through every layer to its destination, such as route to middleware to service to database. Each slice must cover the entry point, every layer, a call sequence diagram, at least one error path, and cross-links.

All output is written to teach/<path>/ at the workspace root, where <path> comes from the .gitmodules logical project path. Writing to .agents/ or any non-teach/ path is strictly forbidden and validated before goals can be marked done.

After the goal queue empties, it diffs all repository source files against files referenced in generated docs. Missing files spawn supplementary L3 goals, and the loop repeats until the diff is empty and the Definition of Done checklist passes.

Goals with Critical review issues are marked needs_fix and sent back to a teach subagent for repair, with at most two fix-review cycles. Goals still failing after that, or after three execution retries, are marked blocked and listed in the final report for human intervention.

No file may be completely skipped; the rules only allow reducing detail level. Third-party vendor code, auto-generated files, binaries, and test fixtures can be exempted, but each exemption must be listed with a justification in the L0 phase.