| title | Core Concepts | ||
|---|---|---|---|
| description | Understand the key concepts that power Jumbo — sessions, goals, context packets, and project knowledge. | ||
| sidebar |
|
Understand the key concepts that power Jumbo.
Sessions provide agents with managed metadata about project work.
Starting a session renders a workflow router:
- A session ID and status
- A prompt asking which workflow the user wants
- Commands for design/define, refine, execute, review, and codify workflows
Ending a session captures what was accomplished, creating a book of record for the project history.
jumbo session start
# ... work with your AI agent ...
jumbo session end --focus "Completed authentication module":::note Session commands are designed for agents to use, but it's perfectly safe to run them yourself to explore what gets rendered. You won't break anything. :::
Goals are discrete units of work that move through a four phased lifecycle. Each goal has:
| Property | Description |
|---|---|
| Title | Short label for the goal (max 60 characters) |
| Objective | What needs to be accomplished |
| Criteria | Success criteria that must be satisfied for approval |
| Scope in | Components, files, or namespaces in scope for the goal |
| Scope out | Components, files, or namespaces explicitly out of scope |
| Next goal | Goal to chain to after this one completes |
| Previous goal | Goal that chains into this one |
| Prerequisite goals | Goals that must be completed before this goal can start |
| Status | Current lifecycle state (see below) |
| Status | Phase | Description |
|---|---|---|
defined |
Definition | Goal created, not yet refined |
in-refinement |
Refinement | Relations to project entities being curated |
refined |
Refinement | Refinement complete, ready to start |
doing |
Execution | Currently being implemented |
paused |
Execution | Temporarily paused (context compressed, work paused, etc.) |
blocked |
Execution | Impeded by an external factor |
unblocked |
Execution | Blocker resolved, transitioning back to doing |
submitted |
Review | Implementation complete, awaiting QA review |
in-review |
Review | QA review in progress |
rejected |
Review | QA review failed, needs rework |
approved |
Review | QA review passed |
codifying |
Codification | Architectural reconciliation in progress |
done |
Complete | Goal closed after codification |
When you start a goal, Jumbo delivers a context packet containing everything your AI agent needs to work effectively.
jumbo goal add --objective "Add dark mode" --criteria "Toggle works" "Persists preference"
jumbo goal refine --id <id>
jumbo goal commit --id <id>
jumbo goal start --id <id>Context packets are optimized bundles of project knowledge delivered at workflow transitions.
Session start packet contains:
- Session ID and status
- Workflow choice prompt
- Route commands for loading the next workflow-specific context packet
Project north-star packet contains:
- Project overview
- Audiences
- Audience pains
- Value propositions
Goal start packet contains:
- Goal objective, criteria, and boundaries
- Relevant components and dependencies
- Applicable invariants and guidelines
- Related decisions
Context packets are designed for minimal token usage while providing maximum relevance.
Jumbo captures several types of project knowledge:
| Type | Purpose |
|---|---|
| Components | Parts of your system and their responsibilities |
| Decisions | Architectural decisions and their rationale |
| Invariants | Non-negotiable rules your code must follow |
| Guidelines | Coding standards and best practices |
| Dependencies | External systems and libraries |
| Audiences | Who uses your product and their priority |
| Audience Pains | Problems your audiences face |
| Value Propositions | How your product addresses audience pains |
| Relations | Connections between goals and knowledge entities |
This knowledge is delivered to your AI agent when relevant to the current goal.
- Goal management guide — Master the goal lifecycle