intent-cli

Category: Tools & Productivity | Uploader: dozybot001 | Downloads: 0 | Version: v1.0（Latest）

Use when you need to operate the Intent CLI semantic history layer in a Git repository.

Changelog: Source: GitHub https://github.com/dozybot001/Intent

Directory Structure

Current level: skills/intent-cli/

📁 agents/
- 📄 openai.yaml 214 B
📁 references/
- 📄 dogfooding.md 757 B
- 📄 error-handling.md 973 B
- 📄 query-examples.md 1.4 KB
- 📄 workflow-cheatsheet.md 886 B
📄 SKILL.md 2.1 KB

SKILL.md

---
name: intent-cli
description: Use when you need to operate the Intent CLI semantic history layer in a Git repository.
---

# Intent CLI

Intent records semantic history on top of Git: what problem you worked on, what you did, and why.

## Core loop

```bash
itt init                              # initialize
itt start "Describe the problem"      # open an intent
itt snap "What I did" -m "Why"        # record a checkpoint (adopted by default)
itt done                              # close the intent
itt inspect                           # read workspace state (primary read interface)
```

## Commands

All output is JSON. No flags needed.

| Command | Purpose |
|---------|---------|
| `itt init` | Initialize `.intent/` in a Git repo |
| `itt start <title>` | Create and activate an intent |
| `itt snap <title> [-m why]` | Record a checkpoint (adopted by default) |
| `itt snap <title> --candidate` | Record without adopting (for comparison) |
| `itt adopt [cp-id] [-m why]` | Adopt a candidate checkpoint |
| `itt revert [-m why]` | Revert last adopted checkpoint |
| `itt done [intent-id]` | Close the active intent |
| `itt inspect` | Machine-readable workspace snapshot |
| `itt list <intent\|checkpoint>` | List objects |
| `itt show <id>` | Show a single object |

## Protocol

1. Run `itt inspect` before substantive work.
2. If not initialized, run `itt init`.
3. If no active intent, run `itt start`.
4. Use `itt snap` for meaningful steps. Default is adopted — use `--candidate` only when comparing alternatives.
5. Run `itt inspect` after state-changing commands.
6. Run `itt done` when the intent is resolved.

## Object model

Two objects:

- **Intent**: the problem being worked on (`open` → `done`)
- **Checkpoint**: a recorded step with rationale (`adopted`, `candidate`, or `reverted`)

## Workspace status

- `idle` — no active intent
- `active` — intent is open
- `conflict` — multiple candidates need resolution

## Guardrails

- Do not invent object IDs.
- Do not create noisy checkpoints for trivial edits.
- If you skip Intent during substantive work, explain why.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

intent-cli

Directory Structure

SKILL.md

Report

Notice