Intake Pile
The intake pile is a lightweight capture layer for bugs and ideas. File something in seconds; Jig’s AI triage matches it to the right spec in the background.
Bugs vs ideas
| Type | When to use |
|---|---|
bug | Something is broken or behaving unexpectedly |
idea | A feature suggestion or improvement thought |
Both types go into the same pile and appear in jig findings. The type affects triage priority: bugs are surfaced before ideas and are more likely to be promoted to tasks.
Capture channels
CLI
# File a bugjig bug "Login button does nothing when clicked on mobile"
# File an ideajig idea "Let users pin their most-used specs to the top of the list"MCP (from Claude)
When you describe a bug or idea in conversation, Claude can file it immediately:
User: Oh, I just noticed the sidebar doesn't close after you navigate.Claude: [calls file_bug with content and conversation context] Filed bug #bug-3a9f. Triage running in background.Triage
After a finding is filed, Jig runs AI triage asynchronously:
- Reads the finding description
- Compares against existing spec intents and file scopes
- Suggests the most relevant spec
- Assigns a severity (bugs only: low / medium / high)
- Updates the finding status from
newtotriaged
Triage results appear when you run jig findings.
Reviewing findings
# List all active findingsjig findings
# Filter to bugs onlyjig findings --bugs
# Filter to ideas onlyjig findings --ideasExample output:
[bug] #bug-3a9f sidebar-navigation high Sidebar doesn't close after navigation on mobile Suggested spec: dashboard-ui
[idea] #idea-7c12 (untriaged) Pin most-used specs to top of listPromotion
To turn a finding into a task, create or update a spec using the finding as context. The typical flow:
jig findings— review what’s accumulatedjig spec show <suggested-spec>— read the spec- Add a task manually via
create_task(MCP) orjig decompose(CLI) with the bug description as context jig dismiss <id>— dismiss the finding once the task is created
Dismissing findings
jig dismiss bug-3a9fDismissed findings are hidden from jig findings output but are not deleted. They remain in history.
CLI commands
See CLI Reference for bug, idea, findings, and dismiss.