deep-plan

Capture branch, PR, and file context into a structured Context Brief before plan mode.

29|4|Updated Jan 12, 2026

Search Tags:#planning #handoff #branch #pull-request #plan-mode #context-preservation #workflow-coordination

Ready to run

npx skills add https://github.com/matsen/bipartite --skill deep-plan-matsen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deep-plan
Source: https://github.com/matsen/bipartite/tree/main/skills/deep-plan
Command: npx skills add https://github.com/matsen/bipartite --skill deep-plan-matsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode can clear conversation history, risking loss of important planning context. This skill captures and preserves branch, PR, and file context before entering plan mode, ensuring a handoff-ready brief is available.

Core Features & Use Cases

Context capture: collects git state, PR data, and relevant changes prior to planning.
Context Brief generation: assembles a structured briefing for the planning agent.
Activation and reporting: hands off to plan mode and provides a post-use summary.

Quick Start

Run /deep-plan to capture current context and prepare a handoff-ready plan.

Frequently Asked Questions about deep-plan

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

FAQPage Schema

How do I preserve planning context before plan mode clears conversation history?▼

To preserve planning context before plan mode clears conversation history, you can capture the current git branch, pull request data, and file changes to generate a handoff-ready Context Brief before activating plan mode.

What is a handoff-ready Context Brief in software development workflows?▼

A handoff-ready Context Brief is a structured summary of your current git repository state, pull request reviews, and relevant file history, ensuring that a planning agent receives all necessary context before starting a new task.

How do I prepare a structured planning brief across git repositories and pull requests?▼

Preparing a structured planning brief involves gathering your current git state, PR data, and relevant file changes, then assembling them into a structured briefing that activates workflow coordination for the planning agent.

Can I use plan mode without losing my current branch and pull request context?▼

Yes, you can use plan mode without losing your current branch and pull request context by capturing git state and PR data beforehand, assembling a Context Brief, and then handing off to plan mode with full context preserved.

Does entering plan mode automatically clear conversation history in workflow coordination?▼

Entering plan mode can clear conversation history, which risks losing important planning context, but you can prevent this by capturing branch, PR, and file context first to ensure a handoff-ready brief remains available.

What are the limitations of preserving context manually before activating plan mode?▼

Manual context preservation before activating plan mode risks missing relevant changes or git state if not fully captured, which is why an automated workflow gathers context, composes a brief, and activates plan mode to ensure nothing is lost.

Nick777-Pixel