
Tdp Plugins
Manage a .context/ task-driven development workspace—vision, epics, breakdown, TDD tasks—and pull library/framework reference guides on demand.
Overview
tdp-plugins is a plugin marketplace for the Build phase that provides ctx for .context/ task-driven development and libref for library and framework reference guides.
What is this marketplace?
- ctx (MIT, v2.0.5): full .context/ workflow—project setup, vision, architecture, tech stack, epic planning, investigate,
- libref (v0.1.0): library and framework reference guides, conventions, and API-oriented tool docs
- Keywords span task-driven development, epic breakdown, and project-setup automation
- 2-plugin marketplace by Phuong Tran (tdp1999) with repository at github.com/tdp1999/claude-code-ctx
- Marketplace bundles 2 plugins: ctx and libref
- ctx version 2.0.5 (MIT); libref version 0.1.0 (MIT)
What problem does it solve?
Agent sessions lose epic scope, architecture decisions, and task state when context lives only in chat history.
Who is it for?
Solo builders running long-horizon Claude Code projects who want file-backed vision, planning, and framework docs beside the repo.
Skip if: One-off scripts with no recurring PM needs, or teams that only want a single integration MCP without local context files.
What do I get? / Deliverables
After adding the marketplace, you get a structured .context/ workspace with epics, tasks, TDD tracking, and pullable library references inside Claude Code.
- Structured .context/ artifacts: vision, architecture, tech stack, epics, tasks, and progress
- Framework and library reference snippets via libref during implementation
Plugins in this marketplace
2 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
ctx establishes project vision, architecture, epics, and task tracking at the start of implementation, which is the Build pm lane for solo builders. Both ctx and libref support planning, investigation, and consistent conventions during active development—not distribution or production ops.
How it compares
Task-driven .context/ workflow marketplace, not a hosted project-management SaaS or deploy pipeline.
Common Questions / FAQ
Who is Tdp Plugins for?
It is for Claude Code users—often indies shipping multi-epic products—who need persisted vision, tasks, and library references via ctx and libref.
When should I use Tdp Plugins?
Use it at project kickoff and throughout Build when you are defining architecture, breaking epics into TDD tasks, or needing authoritative framework guides.
How do I add Tdp Plugins to my agent?
Install the tdp1999/claude-code-ctx marketplace in Claude Code, enable ctx and libref, and initialize or adopt the .context/ folder workflow in your repo.