goodtek vibepulse % vibeops init
Agent clients
Which coding agents will you use? (Space toggle · Enter confirm) Cursor
(.cursor/rules, .cursor/skills)
Branch policy
Branch policy GitFlow lite — develop (integration) + main (production)
→ vibeops init → /Users/hjhamm/goodtek/vibepulse
project: vibepulse
vibeops: 2.3.0
clients: Cursor (.cursor/rules, .cursor/skills)
git: integration=develop, production=main
✓ created .cursor/rules/01-task-source-of-truth.mdc
✓ created .cursor/rules/02-git-safety.mdc
✓ created .cursor/rules/03-docs-before-ship.mdc
✓ created AGENTS.md
✓ created docs/logs/README.md
✓ created docs/project/03-architecture.md
✓ created docs/project/05-current-state.md
✓ created docs/project/06-decisions.md
✓ created docs/tasks/TASK-000-template.md
✓ created .cursor/skills/implement-task/SKILL.md
✓ created .cursor/skills/plan-task/SKILL.md
✓ created .vibeops.json
✓ created .vibeops.env.example
✓ created .gitignore
done: 14 created, 0 overwritten, 0 skipped.
Git repository
Create initial commit? Yes
Initial commit message initialize vibepulse project
Git setup:
✓ git init
✓ production branch main
✓ initial commit on main
✓ integration branch develop
Remote origin is required for push and merge requests.
GitHub repository name (owner/repo or name for gh to create) vibepulse
Creating GitHub repository via gh…
Remote bootstrap:
✓ pushed main → origin
✓ pushed develop → origin
Next steps:
- Read AGENTS.md
- Cursor: @docs/tasks/TASK-001-….md in Ask, then Agent (+ /plan-task, /implement-task)
- vibeops llm connect — LLM for task add / task ship
- Push branches to origin (first time only):
git push -u origin main
git push -u origin develop - vibeops task add — branches from develop (pulls latest first)
- vibeops task ship → merge → sync — TASK lifecycle on github
goodtek vibepulse %