harness-engineering-guide

Log a manual observation about the current session. Invoke when the user runs /case-study-capture to record something noteworthy that automatic hooks cannot detect -- a successful pattern, a human override, a context architecture insight, or friction the hooks missed.

Synthesize all captured observation data into a case study draft and a harness guide improvement plan. Invoke when the user runs /case-study-synthesize at build completion or at any milestone where a synthesis snapshot is useful.

Create GitHub pull requests with deterministic commands, transient failure recovery, and content validation. Use when creating a pull request to ensure the final PR body on GitHub matches what was intended.

Invoke this skill when the user asks to implement, take, pick up, work on, tackle, start, or grab a GitHub issue. Triggers on phrases like "implement issue

Invoke this skill after any structural change to the repository — renaming files, changing chapter H1 titles, adding or removing chapters or templates, updating canonical terms, or modifying template paths. Also invoke when the user asks to "check cross-references", "validate links", or "verify chapter titles match README". The guide-chapter rule directs you to run this after structural edits.

Phase completion checklist -- verifies tests, integration, state, and PR readiness before marking a phase done.

Create GitHub issues with deterministic commands, transient failure recovery, and content validation. Use when creating one or more GitHub issues to ensure the final issue body on GitHub matches what was intended.

Anti-generic design enforcement -- catches AI-generated visual antipatterns and verifies brand compliance.

Invoke this skill before making substantive edits to any file in guide/ — changing content, titles, template references, or canonical terms. Follow this workflow proactively when editing chapters, not only when the user explicitly requests it. Ensures structural changes propagate to all dependent files.