Feature Tree
Install to track features in AI coding sessions, link work to symbols and commits, and carry context across Claude Code sessions.
Overview
Feature Tree is a plugin marketplace for the Build phase that bundles AI-driven feature tracking linked to code and a session-memory companion for Claude Code.
What is this marketplace?
- feature-tree plugin (v3.1.0): AI-driven feature management with links to code symbols and commits
- ft-mem plugin (v3.0.0): session handoffs and persisted project knowledge between sessions
- Two-plugin marketplace bundle aimed at Claude Code feature and memory workflows
- Tracks features as first-class artifacts instead of scattered chat notes
- Pairs delivery tracking with continuity so agents do not restart from zero each session
- Marketplace lists 2 plugins: feature-tree v3.1.0 and ft-mem v3.0.0
Community signal: 1 GitHub stars.
What problem does it solve?
Agent sessions lose feature status and project context, so builders re-explain scope and cannot see which commits or symbols actually implement a feature.
Who is it for?
Solo builders using Claude Code who want feature lists tied to symbols/commits and reliable session-to-session continuity on one codebase.
Skip if: Teams that already enforce full traceability in Jira/Linear with no agent workflow, or projects that need only one-off snippets without ongoing feature tracking.
What do I get? / Deliverables
After adding the marketplace, features stay linked to the codebase and handoff context persists so the next session continues with accurate scope and history.
- Installed feature-tree and ft-mem plugins from one marketplace
- Feature records linked to implementation in the codebase
- Persisted handoff context for the next agent session
Plugins in this marketplace
2 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Feature trees and commit-linked scope live where you design and ship product work, so the canonical shelf is Build even though session memory helps later Operate work. Primary value is product/feature management and traceability to code, which maps to the pm subphase rather than a single integration or frontend task.
How it compares
Claude Code plugin marketplace with two PM and memory plugins, not a single MCP server or generic skills.sh skill pack.
Common Questions / FAQ
Who is Feature Tree for?
Indie and solo developers on Claude Code who manage features in the agent and want those features connected to real code and commits, with memory across sessions.
When should I use Feature Tree?
Use it during active Build work when features multiply across chats and you need structured tracking plus ft-mem handoffs before long breaks or context resets.
How do I add Feature Tree to my agent?
Register or install the Feature Tree marketplace in Claude Code, then enable both the Feature Tree and ft-mem plugins from the bundle so tracking and session continuity work together.