teach

Convert completed task artifacts into an operator-facing teaching packet with verification evidence.

28|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/mifunedev/openharness --skill teach-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/teach
Command: npx skills add https://github.com/mifunedev/openharness --skill teach-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms completed task artifacts into a clear, operator-facing mental model that aligns documented knowledge with what shipped.

Core Features & Use Cases

  • Aligns the knowledge model with shipped behavior by reviewing task artifacts and wiki entries.
  • Proposes targeted wiki edits or new entries when the provisional model needs updating, with evidence citations.
  • Generates a teaching packet including verification evidence and understanding checks to confirm operator comprehension.

Quick Start

Invoke /teach <task-slug> to convert completed task artifacts into an operator-facing teaching packet, optionally specifying --wiki <slug> to target a specific knowledge entry.

Frequently Asked Questions about teach

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update wiki entries to match what actually shipped after implementation?

To update wiki entries after implementation, you can review completed task artifacts like prd.md, progress.txt, and audit notes to propose targeted wiki edits. This aligns your documented knowledge model with the actual shipped behavior using cited verification evidence.

What is knowledge transfer for operators in a post-implementation scenario?

Knowledge transfer for operators in a post-implementation scenario is the process of converting completed task artifacts into a clear, operator-facing mental model. It generates a teaching packet with verification evidence and comprehension checks to confirm operator understanding.

What task artifacts do I need to generate an operator teaching packet?

Generating an operator teaching packet requires access to task artifacts such as prd.md, prd.json, progress.txt, critique.md, evals, and audit notes. An existing wiki entry is also required to produce a structured teaching output with a final model and checks.

Can I specify a specific wiki entry when creating post-implementation documentation updates?

Yes, you can specify a specific wiki entry when creating post-implementation documentation updates by using the --wiki <slug> parameter. This targets a particular knowledge entry for revision when implementation changes require updating the provisional model.

How do I verify operator comprehension after updating project documentation?

To verify operator comprehension after updating project documentation, a teaching packet is generated that includes verification evidence and understanding checks. This ensures the operator grasps the revised mental model aligned with the shipped behavior.

What is the best way to align documented knowledge with shipped behavior?

The best way to align documented knowledge with shipped behavior is to transform completed task artifacts into an operator-facing mental model. This process reviews implementation evidence to propose targeted wiki edits, ensuring documentation accurately reflects the final product.