codify-jumbo-goal
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation…
Use liberally when you discover or are told a non-negotiable constraint — something that must always be true regardless of context. Registers the invariant so future sessions never violate it.
$ npx -y skills add jumbocontext/cli --skill jumbo-add-invariant --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/jumbo-add-invariantContext preview
The summary Claude sees to decide when to auto-load this skill.
Use liberally when you discover or are told a non-negotiable constraint — something that must always be true regardless of context. Registers the invariant so future sessions never violate it.
name: jumbo-add-invariant description: Use liberally when you discover or are told a non-negotiable constraint — something that must always be true regardless of context. Registers the invariant so future sessions never violate it.
Register an invariant with Jumbo when you discover a non-negotiable constraint — a rule that must hold true across the entire project at all times, regardless of which goal is being implemented.
**Important:** Invariants must be **generally applicable** to the project. Do not word them for a specific use case, goal, or task. An invariant that only applies during one piece of work belongs in a goal's criteria, not in the invariant registry. If you find yourself writing "when working on X" or "for the Y feature", it is not an invariant.
Check for an existing invariant to avoid duplication. Consider reversing, updating, or superseding a previously registered invariant before registering a new one.
Use the search subcommand to locate previously registered invariants:
jumbo invariants search -q <query>
jumbo invariant add \ --title "<Invariant title>" \ --description "<What must always be true>" \ --rationale "<Why this is non-negotiable>"
jumbo invariant add \ --title "Session endpoint must validate tokens" \ --description "The /api/session endpoint must check JWT expiry" \ --rationale "Security requirement for session management"
Too narrow — applies to one endpoint. This is a requirement for a specific feature, not a project-wide invariant.
jumbo invariant add \ --title "All API endpoints must validate authentication tokens" \ --description "Every endpoint that accepts authenticated requests must verify token validity, expiry, and scope before processing the request" \ --rationale "Security compliance requirement — unauthenticated access to protected resources is a critical vulnerability"
Applies to every endpoint, not just one. States the full constraint. Rationale explains why violation is unacceptable.
Repo: jumbocontext/jumbo.cli
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation…
Use when a project has Architecture data that needs migrating to fine-grained entities…
Add Jumbo goals liberally to decompose objectives into finite units of work with bounded…
Use when the user's prompt is delivered outside the execution context of an existing Jumbo…
Use liberally when you create, discover, or modify a software component. Registers the…
Use liberally when you make an architectural choice, select a technology, or reject an…