T-Plan Task Orchestrator FAQs

Question 1

Where does T-Plan store its planning artifacts?

Accepted Answer

T-Plan creates a .t-plan directory in your project root, organizing session-specific files like intent.md, explore.md, and the final plan.md for future reference.

Question 2

What is the primary purpose of the T-Plan skill?

Accepted Answer

T-Plan is designed to act as an orchestrator that manages a structured planning process for complex features, ensuring all architectural decisions are explored and validated before implementation begins.

Question 3

How does the 'Validate' step work in T-Plan?

Accepted Answer

A specialized subagent uses tools like WebSearch to check the draft implementation plan against official documentation to ensure there are no deprecated APIs or anti-patterns.

Question 4

When should I use T-Plan instead of standard Claude Code commands?

Accepted Answer

Use T-Plan for multi-file features, major architectural changes, or when working with unfamiliar technologies that require research. Skip it for quick fixes or single-file changes.

Question 5

Does T-Plan automatically modify my source code?

Accepted Answer

No, T-Plan is an orchestrator for planning. It focuses on generating a validated implementation strategy. Once you approve the plan, you can then proceed to execution.

T-Plan Task Orchestrator

Key Features

Use Cases

T-Plan Task Orchestrator

Key Features

Use Cases