teach-charter

Generates inclusion-config.md with decisions, priorities, and active checks for your project.

5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill teach-charter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teach-charter
Source: https://github.com/hereinthehive/gotrino-inclusion/tree/main/skills/teach-charter
Command: npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill teach-charter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to set up the inclusion plugin for a project, capturing context and scope decisions and generating a central config that evolves with the project.

Core Features & Use Cases

  • Discovers project context (tooling, stack, tests, docs) and suggests scope boundaries.
  • Captures and persists decisions in inclusion-config.md to minimize nagging and ensure consistent checks.
  • Supports updating decisions over time and re-running setup as the project evolves.

Quick Start

Run the command to configure your project and generate the initial inclusion-config.

Frequently Asked Questions about teach-charter

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

FAQPage Schema
How do I configure inclusion checks for a new software project?▼

Run the setup command to auto-detect your project context and generate an inclusion-config.md file that captures your scope boundaries, active checks, and decisions to guide consistent inclusion validation.

What is an inclusion-config.md file used for?▼

An inclusion-config.md file persists your project's inclusion decisions, priorities, and active checks to minimize tooling nagging and ensure consistent validation as the project evolves over time.

How do I update inclusion scope boundaries as my project stack changes?▼

Re-run the setup process to capture new decisions regarding your stack and tooling. This updates the inclusion-config.md, preserving your evolving scope boundaries and priorities for future checks.

Can I auto-configure inclusion decisions for common development stacks?▼

Yes, the setup process auto-detects common project stacks, tooling, tests, and docs to suggest scope boundaries and generate a tailored inclusion configuration automatically.

Why do I need to persist inclusion decisions in a central config file?▼

Persisting inclusion decisions in a central config file minimizes nagging from repeated prompts and ensures consistent checks across your tooling by maintaining a clear record of priorities and active checks.

Does the inclusion setup work with existing project documentation and tests?▼

Yes, the setup discovers existing project context including documentation and tests to accurately suggest scope boundaries and configure appropriate inclusion checks for your current workflow.