crave

Commit current changes. Use when: committing work, grouping changes into atomic commits, staging and committing, creating conventional commits. Groups related changes into well-scoped atomic commits with clear messages.

Plan a new CraveDB feature end-to-end. Use when: adding a new capability, designing a subsystem, planning a new module, proposing architecture changes. Produces a numbered design document in design/ and actionable checklist items in design/11-implementation-phases.md.