Kecbigmt Cc Plugins
- Updated February 4, 2026
- kecbigmt/cc-plugins
kecbigmt-cc-plugins is a Claude Code plugin that provides story-driven development commands and remote dev-server access utilities for user-story-led delivery.
About
kecbigmt-cc-plugins is a two-plugin Claude Code collection aimed at developers who want software delivery to follow user stories instead of ad-hoc prompts. The story-driven side emphasizes acceptance criteria, verification, and TDD-friendly workflow so Claude Code works against explicit outcomes rather than vague tasks. The companion networking utilities extend that loop when your dev server or test environment lives elsewhere—you configure remote access patterns (including Tailscale/VPN-oriented keywords) so the same story context survives off-machine debugging. Install it when you are past pure ideation and need a repeatable PM layer inside the terminal: slice features as stories, attach criteria, run verification, and optionally hit a remote dev server without rewriting your process each sprint. It is a workflow plugin pack, not a hosted backlog product or a full CI platform. Expect to bring your own repo conventions and test stack; the plugins orchestrate how Claude Code interprets stories, commands, and access—not replace product analytics or production monitoring.
- Two-plugin Claude Code bundle: story-driven development workflow plus networking-oriented utilities
- Story-driven commands for user stories, acceptance criteria, and verification aligned with TDD habits
- Skills and commands surfaced for structured story creation and management inside the agent
- Remote-access and Tailscale/VPN-related helpers for reaching dev servers from Claude Code sessions
- Categories span development-workflow and networking for solo builders pairing PM ritual with remote environments
Kecbigmt Cc Plugins by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install kecbigmt-cc-plugins@kecbigmt/cc-pluginsAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | February 4, 2026 |
|---|---|
| Repository | kecbigmt/cc-plugins ↗ |
What it does
Run story-driven development in Claude Code with user stories, acceptance criteria, TDD-style verification, and optional remote dev-server access over Tailscale.
Who is it for?
Best when you're practicing story-driven or TDD-aligned delivery and want Claude Code commands for stories plus Tailscale-friendly remote dev access.
Skip if: Skip if you want a single integration with no PM ceremony or teams that do not run user stories in the terminal at all.
What you get
After you add the bundle, Claude Code can follow story-driven workflows with criteria and verification—and optionally reach remote dev servers—so each slice has a testable finish line.
- Story-driven Claude Code command workflow with criteria and verification hooks
- Configured remote-access path to dev servers when using the networking plugin
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Story-driven Claude Code workflow pack with networking utilities, not a standalone project-management SaaS.
FAQ
Who is Kecbigmt Cc Plugins for?
It is for and small-team developers who manage work as user stories in Claude Code and sometimes need remote dev-server access.
When should I use Kecbigmt Cc Plugins?
Use it when scoping features into stories with acceptance criteria and when you want agent commands to respect that story-driven, verification-first loop.
How do I add Kecbigmt Cc Plugins to my agent?
Register both plugins from the kecbigmt/cc-plugins repository in Claude Code, configure remote-access pieces like Tailscale if needed, then invoke the story-driven commands from your project root.