novibe
Drive a change the NoVibe way: a Gherkin spec, then a C4 design, then BDD — one small slice at a time, pausing for the driver's call between steps. Use for any change beyond a typo, or when asked to build something the NoVibe way.
Install
npx skills add https://github.com/novibe-org/novibe/tree/main/plugins/novibe/skills/novibe
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install novibe-org-novibe@llmmart
git clone https://github.com/novibe-org/novibe.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole novibe-org/novibe collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
NoVibe
The driver decides; the machine builds what they decided. Any change beyond a typo runs these steps in order, for one small slice:
- Give the slice a branch — on the default branch? Switch to a branch named for the slice.
- Requirements — invoke
requirements-engineer. - Architecture — when the slice brings a new component, framework, technology or integration,
or changes who talks to whom: invoke
architect. Otherwise say in one line why the model stays as it is, and go on. - Build — only once the driver has selected a small slice, every other scenario tagged
@backlog: invokedeveloper, pointed at the spec, the model and the ADRs; never restate what they decide.
One slice, one session — every step runs here, never in a subagent: requirements and architecture are interviews, and the build needs what the driver decided along the way. To work slices in parallel, give each its own session — an agentbox session, or a git worktree each. Move on only when the driver agrees the step is done.
Skipping is the driver's call. A step that looks unnecessary — propose skipping it and wait for an explicit yes; a slice that changes no structure skips the architecture by the rule above. No spec, no model, no tests yet means create the first one, not skip the step.
Files (novibe)
-
SKILL.md 1.6 KB
--- name: novibe description: "Drive a change the NoVibe way: a Gherkin spec, then a C4 design, then BDD — one small slice at a time, pausing for the driver's call between steps. Use for any change beyond a typo, or when asked to build something the NoVibe way." --- # NoVibe **The driver decides; the machine builds what they decided.** Any change beyond a typo runs these steps in order, for one small slice: 1. **Give the slice a branch** — on the default branch? Switch to a branch named for the slice. 2. **Requirements** — invoke `requirements-engineer`. 3. **Architecture** — when the slice brings a new component, framework, technology or integration, or changes who talks to whom: invoke `architect`. Otherwise say in one line why the model stays as it is, and go on. 4. **Build** — only once the driver has selected a small slice, every other scenario tagged `@backlog`: invoke `developer`, pointed at the spec, the model and the ADRs; never restate what they decide. **One slice, one session** — every step runs here, never in a subagent: requirements and architecture are interviews, and the build needs what the driver decided along the way. To work slices in parallel, give each its own session — an [agentbox](https://github.com/novibe-org/agentbox) session, or a git worktree each. Move on only when the driver agrees the step is done. **Skipping is the driver's call.** A step that looks unnecessary — propose skipping it and wait for an explicit yes; a slice that changes no structure skips the architecture by the rule above. No spec, no model, no tests yet means create the first one, not skip the step.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.