tdd-session-clear

Delete handoff.md from a design directory after confirmation.

4|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-session-clear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-session-clear
Source: https://github.com/CurtisThe/three-pillars-plugin/tree/main/skills/tdd-session-clear
Command: npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-session-clear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wipes the handoff.md from a design directory when switching to a completely different task to prevent stale context from contaminating the next session.

Core Features & Use Cases

  • Resolve the design directory path docs/tdd-designs/<design-name>/
  • Check for existence of handoff.md; if absent, inform user.
  • Show a brief 2-3 line summary of the current handoff (phase and key state) for confirmation.
  • Prompt for confirmation before deletion.
  • Delete docs/tdd-designs/<design-name>/handoff.md and confirm deletion.

Quick Start

Run tdd-session-clear with the target design name to remove its handoff.md and reset the session context.

Frequently Asked Questions about tdd-session-clear

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

FAQPage Schema
How do I clear stale handoff context when switching design tasks?

Clear stale handoff context by deleting the handoff.md file from the design directory in docs/tdd-designs/ before starting a new session. This prevents outdated phase and state information from contaminating the next task.

What does a session handoff file contain in a TDD design workflow?

A session handoff file stores phase and key state information for a specific design task. It provides context so the next session can resume work, but must be cleared when switching to a completely different design task.

How do I reset the session state for a TDD design task?

Reset the session state by removing the handoff.md file from the target design directory. The system validates the design name, shows a brief summary of the current handoff, prompts for confirmation, and deletes only that file.

Do I need a valid design name to delete a handoff file?

Yes, the system validates the target design name against shared naming rules before checking if handoff.md exists. This ensures it only deletes files in properly named design directories within docs/tdd-designs/.

What happens if the handoff.md file is already absent when clearing a session?

If the handoff.md file is already absent, the system informs you that no deletion is needed. It checks for the file's existence before prompting for confirmation to ensure a clean session state.