I built Vibe Coding Production Kit (VCP) because AI-assisted development often solves the easiest part first: generating code.
The harder part is keeping requirements, architecture, security, testing, review, and production changes coherent over time.
VCP makes the repository the source of truth and gives coding agents a structured workflow:
Idea → Product Spec → UX → Domain → Architecture → Security → Backlog → AI Context → Implementation → Verification → Review → CI/CD → Production → Observability → Maintenance
The CLI currently supports:
- `vcp init` - `vcp task` - `vcp ready` - `vcp context` - `vcp verify` - `vcp doctor` - `vcp update` - `vcp rollback` - `vcp manage ignore` - `vcp manage track`
The major addition in v0.9 is safe project lifecycle management.
Initialized projects now keep manifest state and tracked baselines, allowing VCP to distinguish upstream framework changes from local project decisions.
Updates support: - dry-run planning - ownership-aware behavior - bounded three-way merge - explicit migrations - conflict blocking - transactional backups - rollback - lifecycle locking - baseline integrity checks
The package has zero runtime dependencies and requires Node 22+.
Install: `npx vibe-coding-production init . --agent all --stack auto --yes`
GitHub: https://github.com/Moeeryani/Vibe-Coding-Production-Kit
npm: https://www.npmjs.com/package/vibe-coding-production
Release: https://github.com/Moeeryani/Vibe-Coding-Production-Kit/rele...
I’d especially value feedback on: - onboarding - task/readiness workflow - context pack usefulness - update behavior in real projects - where this model breaks down