Before you begin: finish installation and project setup. Open that project folder
in your AI coding app. Everything in a “Send to your agent” box below goes in its chat.
1. Describe your idea
Send to your agent
For developers: the specification and roadmap
For developers: the specification and roadmap
The agent uses
jig-idea to widen the idea with proposals of its own, stress-test assumptions,
and compare alternatives. With no code to read yet, it looks up how others solve the same problem.
You choose easy, normal, or deep exploration; deep includes an independent agent’s challenge.
The level sets the length of one circle of questions. Each circle ends with a summary and the
directions left unopened, and you decide: another circle, or write it down. Nothing is committed
before you say so. Until then the agent keeps the conversation in a draft under
.ai/workspace/ideas/, outside git, in your language: if the session ends early, the next one
picks it up. jig status shows a drafts: line while one exists. A draft is removed when its
specification is committed, or when you ask for it (jig spec draft drop <id>) — never on its own.It then records the result in .ai/specs/<id>/: spec.md, architecture.md, stack.md, and
roadmap.md. The roadmap holds phases, dependencies, parallel waves, and fog: for work that
cannot yet be stated precisely. Replace its example items before using it.Specifications are committed plans. They are not resolved as project knowledge, so future
intentions do not become claims about implemented behaviour. To move a spec to another
project, copy its .ai/specs/<id>/ folder there.2. Give future sessions the same plan
Send to your agent
For developers: how decisions become knowledge
For developers: how decisions become knowledge
jig-init carries decisions into .ai/knowledge/: terms into GLOSSARY.md, boundaries into
ARCHITECTURE.md, invariants into RULES.md, and decisions with alternatives into ADRs.
Component contracts become conventions. Planned architecture is labelled Intended — not built yet.The chosen stack determines verification profiles. Until the project’s tools and manifests exist,
those checks report skips, not passes. The task that implements a part updates its intended status.3. Choose the first thing to build
Send to your agent
Send to your agent
<task-id> with the ID the agent showed you. For our booking app, the first result might
be a class schedule; reservations could be the next task.
If the agent asks you to approve a design, read it before saying yes. You can ask it to explain
a choice, reduce the scope, or change the plan. You do not need to approve something you do not understand.
For developers: tasks, branches, and releases
For developers: tasks, branches, and releases
The agent classifies each task by risk and links it to the spec. Tasks normally branch from
the project’s main branch. If the product will be released once at the end, the agent discusses
an epic branch with you while shaping the roadmap. Its tasks branch from the epic and their
pull requests target it; the main branch receives the combined work when the epic is merged.
jig spec epic <id> creates that branch once the spec is on the main branch. The epic merges the
finished feature without raising the version; the release that ships it is made afterwards, by
the jig-release skill. jig spec ship follows your Git permissions.
Finishing the epic asks about any remaining items, fog, open questions, or ideas set aside before retiring the spec.At consolidation, completed tasks check their roadmap items in the same change as the implementation.
See manual control for task commands and autopilot
for running a whole phase.4. Try the result and give feedback
Follow the agent’s instructions to open the project. For a website this will usually be a local preview: a page on your computer that other people cannot yet visit. Describe what happened and what you expected:Send to your agent
Send to your agent