Obsfx Trekker Claude Code
obsfx-trekker-claude-code is a Claude Code plugin for the Build phase that lets you manage Trekker tasks, epics, and dependencies via agent commands while you code.
by obsfx · github.com/obsfx/trekker-claude-code
Install trekker-claude-code when you want lightweight epic, task, and dependency tracking driven from Claude Code commands instead of a separate heavy PM suite.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install obsfx-trekker-claude-code@obsfx/trekker-claude-codeBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:obsfx/trekker-claude-code") and the paste-ready config with skillselion.get_install_config("plugin:obsfx/trekker-claude-code").
What it does
obsfx-trekker-claude-code connects Claude Code to Trekker, a simple issue and task tracker aimed at builders who want epics, dependencies, and workflows without juggling another bloated project-management UI. The marketplace entry ships one plugin whose keywords emphasize commands, task management, and AI-optimized coding—suggesting you create and advance work items from the same environment where you implement fixes. For solo developers, that tight loop reduces the gap between “what’s next on the board” and “generate the patch,” which is especially valuable when agents can otherwise wander off-scope. Trekker is not a full spec framework or analytics platform; it is deliberately minimal tracker glue for Claude. If your bottleneck is remembering dependencies and finishing sequenced tasks while pair-programming with an agent, this plugin packages that discipline as first-class Claude Code workflows.
Highlights
- Claude Code plugin bridge to the Trekker issue and task tracker
- Commands for epics, tasks, dependencies, and simple workflows
- AI-optimized coding flows tied to managed backlog items
- Single-plugin marketplace entry focused on tracker integration
- Keeps PM structure inside the agent session where code changes happen
Why builders use it
Builders lose thread between Claude-generated work and a clear backlog because issue tracking lives outside the agent session.
After installing the Trekker plugin, epics, tasks, and dependencies stay synchronized with Claude Code commands so agent work tracks real backlog items.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 3 stars, 0 votes.
FAQ
Who is obsfx-trekker-claude-code for?
It is for Claude Code users who already use or want Trekker’s simple epics-and-tasks model inside their coding agent.
When should I use obsfx-trekker-claude-code?
Use it when planning sprints, breaking down epics, or updating task status and dependencies during active development.
How do I add obsfx-trekker-claude-code to my agent?
Install the obsfx/trekker-claude-code marketplace plugin in Claude Code, configure Trekker access per the repo README, then invoke its task and workflow commands from sessions.
Comments
Share how you use obsfx-trekker-claude-code, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.