tdd-session-save

To save session context for TDD handoff continuity, run tdd-session-save with your target design name. It overwrites handoff.md in docs/tdd-designs/<design-name>/ with structured sections for Phase, Decisions, State, Next, Open Questions, and Carried Forward, preserving your progress.

The best way to track TDD design decisions and state is generating a structured handoff.md file. This process captures your current discussion context, validates the design name, and records decisions, state, next steps, and open questions to maintain continuity across switching phases.

You should generate a handoff document when ending or switching phases of a TDD session. Creating a fresh handoff.md at these points ensures your design decisions, current state, and open questions are preserved for the next conversation.

tdd-session-save overwrites existing handoff.md content entirely. It reads any previous handoff file if present, then replaces it with a fresh structured summary of your current session's Phase, Decisions, State, Next, Open Questions, and Carried Forward sections.

You must follow the tool's naming rules for your design directory when saving a session handoff. The skill validates the provided design-name argument against specific naming conventions before writing the handoff.md file to the docs/tdd-designs/ folder.

Your handoff file needs to be gitignored to prevent committing transient session context into version control. The skill ensures handoff.md in the docs/tdd-designs/<design-name>/ directory is appropriately gitignored, keeping your repository clean while preserving local continuity.