Kecbigmt Cc Plugins
kecbigmt-cc-plugins is a Claude Code plugin for the Build phase that provides story-driven development commands and remote dev-server access utilities for user-story-led delivery.
by kecbigmt · github.com/kecbigmt/cc-plugins
Run story-driven development in Claude Code with user stories, acceptance criteria, TDD-style verification, and optional remote dev-server access over Tailscale.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install kecbigmt-cc-plugins@kecbigmt/cc-pluginsBuilt 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:kecbigmt/cc-plugins") and the paste-ready config with skillselion.get_install_config("plugin:kecbigmt/cc-plugins").
What it does
kecbigmt-cc-plugins is a two-plugin Claude Code collection aimed at solo builders 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.
Highlights
- 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
Why builders use it
Coding with an agent without stories and acceptance criteria turns into endless rework and unclear definitions of done.
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.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is kecbigmt-cc-plugins for?
It is for solo and small-team builders 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.
Comments
Share how you use kecbigmt-cc-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.