By nxhung2204
Automate development workflow: specs → stories → issues → GitHub → implementation
npx claudepluginhub nxhung2204/cc-auto-workflow-plugin --plugin cc-auto-workflowCreate issues from specs/story.md file. Use when use ask "Generate issues, generate issue [number].[title]"
Implement a feature from a GitHub Issue. Use when user asks "implement issue 1, implement
Review code against project rules and standards. Use when user asks "review code, review-code issue
Review specification for completeness and clarity. Use when user asks "review spec 1, review-specs
Initialize project structure for auto-workflow plugin
Sync local issue files to GitHub Issues. Use when user asks "sync issues to github" or "push issues to github"
Spec-driven Git workflow plugin with GitHub integration, sprint management, and brownfield migration support for comprehensive development orchestration.
Spec-driven development: structured requirements, tasks, and planning workflows
A workflow automation system that helps Claude Code implement features systematically with built-in planning, validation, and review steps
Autonomous spec-driven development workflow with multi-agent collaboration, specification management, and task orchestration
Spec Driven Development toolkit - structured specification, planning, and implementation workflows for systematic feature development
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Requires secrets
Needs API keys or credentials to function
Share bugs, ideas, or general feedback.
Automate: specs → stories → issues → GitHub → code
After installing the plugin, run the setup skill to initialize your project:
/cc-auto-workflow:setup
Or initialize manually using the setup script:
curl https://raw.githubusercontent.com/nxhung2304/cc-auto-workflow-plugin/main/setup.sh | bash
Or manually initialize:
# 1. Create specs directory
mkdir -p specs/{rules,issues,designs,comments}
# 2. Create your PRD and stories
code specs/prd.md # Write requirements
code specs/story.md # Format: - [ ] [#]. [title]
# 3. Start using commands
/cc-auto-workflow:generate-issues all
bash setup.sh
1️⃣ Create PRD & Stories
code specs/prd.md # Requirements
code specs/story.md # Format: - [ ] [#]. [title]
2️⃣ Generate Issues
/cc-auto-workflow:generate-issues all
3️⃣ Review & Approve
Edit specs/issues/*.md, change pending → approved
4️⃣ Sync to GitHub
/cc-auto-workflow:sync-github-issues
5️⃣ Implement
/cc-auto-workflow:implement-issue 1
| Command | Purpose |
|---|---|
/cc-auto-workflow:generate-issues all | Create issues from stories |
/cc-auto-workflow:sync-github-issues | Push approved issues to GitHub |
/cc-auto-workflow:implement-issue [#] | Implement a specific issue |
/cc-auto-workflow:review-specs [#] | Review issue spec |
/cc-auto-workflow:review-code [#] | Review implementation |
Before /generate-issues:
specs/prd.md ✅specs/story.md ✅Before /sync-github-issues:
approved ✅gh auth login ✅Before /implement-issue [#]:
approved ✅Auto-detects framework:
specs/rules/rails.mdspecs/rules/flutter.mdGitHub (required):
gh auth login
Slack (optional):
export SLACK_BOT_TOKEN=xoxb-xxxxx
export SLACK_CHANNEL_ID=C0AGTJ0EE6B
Follow specs/rules/clean_code.md:
| Problem | Solution |
|---|---|
| setup.sh fails | Check: ls -l specs/ |
| /generate-issues fails | Verify story.md format |
| Can't sync | Run: gh auth login |
| Issue "pending" | Edit → change to approved |
specs/
├── prd.md # Requirements
├── story.md # Tasks
├── issues/ # Generated
├── designs/ # Wireframes
├── comments/ # Reviews
└── rules/ # Standards
specs/rules/clean_code.md — Code standardsOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim