kecbigmt-plugins

kecbigmt's Claude Code Plugins

A collection of Claude Code plugins.

Installation

From Marketplace (Recommended)

# Add the marketplace
/plugin marketplace add kecbigmt/cc-plugins

# Install the story-driven plugin
/plugin install story-driven@kecbigmt-plugins

Plugins

story-driven

Story-driven Development workflow plugin for Claude Code. Provides skills and commands for user story creation, acceptance criteria, verification, and story log management.

codex

Codex CLI integration for autonomous code analysis, reviews, and codebase queries. Executes the codex tool with real-time execution visibility for deep codebase understanding.

Testing Locally

To test plugins during development:

git clone https://github.com/kecbigmt/cc-plugins.git
claude --plugin-dir ./cc-plugins/plugins/story-driven

Restart Claude Code after making changes to pick up updates.

story-driven Usage

/story-driven:start                    # Start workflow (interactive)
/story-driven:start <free text>        # Start with intent

Examples:

/story-driven:start
/story-driven:start add login feature
/story-driven:start verify

codex Usage

The codex plugin provides the codex-exec skill that automatically activates when you request code analysis or reviews.

Examples:

"Review the authentication module for security vulnerabilities"
"Analyze the database query patterns for performance issues"
"Explain how the user registration flow works"
"Find potential bugs in error handling code"

Claude will automatically execute the codex CLI tool with appropriate parameters.

Skills

Skills are model-invoked and activate based on workflow phase.

Skill	Phase
defining-stories	Define
implementing-stories	Implement
verifying-stories	Verify
accepting-stories	Accept
publishing-stories	Publish

Workflow

1. Define → User story with acceptance criteria (in story log)
2. Implement → TDD inner loop (red-green-refactor)
3. Verify → Developer self-testing
4. Accept → Product owner testing (timing flexible)
5. Publish → Commit, push, optionally create PR

Acceptance Testing Flexibility

The timing of acceptance testing adapts to your workflow:

Workflow	Flow
Pre-commit	Verify → Accept → Commit → Push
Pre-push	Verify → Commit → Accept → Push
Post-PR	Verify → Commit → Push → Draft PR → Accept → Ready

Example Usage

Ask Claude naturally:

• "Help me create a user story for adding dark mode"
• "I need to implement the login feature from this story"
• "Run developer verification on my changes"
• "Let's do acceptance testing for the sync-init story"
• "Commit these changes and create a draft PR"

Claude will automatically use the relevant skill.

story-driven Plugin Structure

plugins/story-driven/
  commands/
    start.md                # /story-driven:start command
  skills/
    defining-stories/
    implementing-stories/
    verifying-stories/
    accepting-stories/
    publishing-stories/

License

MIT