context-discipline

Decompose large coding tasks into session-sized chunks with clear done conditions.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/t0lab/harness-kit --skill context-discipline-t0lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-discipline
Source: https://github.com/t0lab/harness-kit/tree/main/.agents/skills/context-discipline
Command: npx skills add https://github.com/t0lab/harness-kit --skill context-discipline-t0lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long AI sessions accumulate stale context, repeated reads, and cascading errors that dilute responses and waste tokens; this Skill restores context hygiene and guides splitting large work into session-sized, verifiable chunks so progress stays reviewable and recoverable.

Core Features & Use Cases

  • Context hygiene: prefer targeted reads over whole-file dumps, use grepping to locate relevant sections, and read with offsets/limits to minimize context load.
  • Session controls: clearly signal context switches and free space with explicit commands such as compacting history for continuity or clearing the session to start fresh.
  • Task decomposition: define committable chunks sized to produce reviewable diffs, clear done conditions, and an ordering of dependencies; include a simple decomposition template and commit-oriented handoff steps.
  • Use cases: planning a large feature across multiple sessions, recovering from repeated failed attempts, managing long debugging sessions, or when the same file is being read multiple times.

Quick Start

Before starting a large coding task, ask the assistant to decompose the work into committable chunks with clear done conditions and to compact or clear context as needed.

Frequently Asked Questions about context-discipline

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

FAQPage Schema
Why does my AI coding session produce cascading errors and repeated file reads?

Long AI sessions accumulate stale context and repeated file reads that dilute responses and waste tokens. Restoring context hygiene through targeted reads and session compaction prevents cascading errors and keeps your coding session focused.

How do I decompose a large feature into manageable coding sessions?

Decompose large feature development by splitting work into committable, session-sized chunks with clear done conditions. This task decomposition creates reviewable diffs and an ordering of dependencies, ensuring progress stays recoverable across multiple sessions.

What is the best way to clear stale context during long debugging sessions?

The best way to clear stale context during long debugging sessions is using explicit session controls. Compacting history preserves continuity while clearing the session starts fresh, immediately freeing space and removing error accumulation.

How do I minimize context load when reading large code files in AI sessions?

Minimize context load by using targeted reads instead of whole-file dumps. Use grepping to locate relevant sections and read with offsets and limits to ensure only necessary code segments enter the AI session.

When should I compact or clear my AI session context?

You should compact or clear AI session context when errors accumulate, the same files are read repeatedly, or before starting a large coding task. Explicit context switches free space and prevent stale context from cascading into new errors.