# imdone.io Site Map

**Last Updated:** February 9, 2026

## Overview
imdone turns Jira and GitHub work into a local product-engineering lab notebook where humans and AI agents share issue context, progress notes, decisions, evidence, blockers, outcomes, and next steps.

---

## Main Pages

### [Homepage](https://imdone.io/)
The shared context problem and how imdone solves it. Choose between CLI and Desktop workflows.

**Keywords:** product engineering lab notes, AI-native backlog, shared working memory

---

## Product Pages

### [imdone CLI](https://imdone.io/imdone-cli)
Command-line workflow for turning Jira and GitHub issues into local product-engineering lab notes.

**Features:**
- Local Markdown backlog for Jira and GitHub issue work
- Progress notes for observations, decisions, evidence, blockers, outcomes, and next steps
- AI-ready story context through `imdone ai` and `imdone hdd`
- Provider sync with Jira and GitHub when useful updates should go back

**Keywords:** product engineering lab notes, AI-native backlog, Jira GitHub issue workspace

### [Markdown Kanban Board](https://imdone.io/markdown-kanban-board)
Visual desktop app with drag-and-drop kanban interface.

**Features:**
- Drag-and-drop markdown TODOs
- Visual board in your editor
- Works with existing markdown
- Desktop app for Mac/Windows/Linux

**Keywords:** markdown kanban, visual task board, desktop app

---

## Team & Enterprise

### [For Teams](https://imdone.io/for-teams)
Collaborative features for engineering teams.

**Features:**
- Ensemble programming support
- Shared context across team
- Team workflows
- Collaborative issue editing

**Keywords:** team collaboration, ensemble programming, shared context teams

### [Markdown Jira Sync](https://imdone.io/markdown-jira-sync)
Bidirectional synchronization between Jira and local markdown files.

**Features:**
- Pull Jira issues to markdown
- Edit locally in any editor
- Sync changes back to Jira
- Keep issues in git history

**Keywords:** Jira markdown sync, bidirectional sync, local Jira editing

### [Markdown GitHub Issues Sync](https://imdone.io/markdown-github-issues-sync)
Bidirectional synchronization between GitHub Issues and local markdown files.

**Features:**
- Pull GitHub Issues to markdown
- Edit locally in any editor
- Sync changes back to GitHub
- Keep issues in git history

**Keywords:** GitHub Issues markdown sync, bidirectional sync, local GitHub editing

---

## Pricing & Plans

### [Plans](https://imdone.io/plans)
Flexible pricing for individuals and teams.

**Plans Available:**
- Free tier
- Individual plans
- Team plans
- Enterprise plans

---

## Resources

### [Documentation](https://imdone.io/docs)
Complete guides for imdone CLI and Desktop.

**Topics:**
- Installation
- Configuration
- Workflow tutorials
- API reference
- Best practices

### [Community](https://imdone.io/community)
Join the imdone community.

**Connect:**
- Discord server
- GitHub discussions
- Community support
- Feature requests

### [Your Backlog Can Be Shared Working Memory For Humans And AI](https://imdone.io/articles/shared-working-memory-for-humans-and-ai)
Article for engineering leaders on using Hypothesis Driven Development to keep story context readable by humans and AI coding assistants.

**Topics:**
- Product-engineering lab notes
- Shared working memory
- Hypothesis Driven Development
- AI-ready story context
- Handoff risk

---

## Legal

### [Privacy Policy](https://imdone.io/privacy)
Privacy policy and data handling practices.

### [EULA](https://imdone.io/eula)
End user license agreement and terms of use.

---

## Site Structure

```
imdone.io/
├── Homepage (/)
├── Product Pages
│   ├── CLI Workflow (/imdone-cli)
│   └── Desktop Workflow (/markdown-kanban-board)
├── Features
│   ├── For Teams (/for-teams)
│   ├── Markdown Jira Sync (/markdown-jira-sync)
│   └── Markdown GitHub Issues Sync (/markdown-github-issues-sync)
├── Pricing (/plans)
├── Resources
│   ├── Documentation (/docs)
│   ├── Community (/community)
│   └── Article: Shared Working Memory (/articles/shared-working-memory-for-humans-and-ai)
└── Legal
    ├── Privacy (/privacy)
    └── EULA (/eula)
```

---

## Core Concepts

**Shared Context Problem:** When issues, decisions, evidence, blockers, and next steps drift away from code and AI sessions, teams lose alignment and adaptability.

**Solution:** Keep the backlog as a local product-engineering lab notebook with issue workspaces in Markdown, next to your code.

**Two Workflows:**
1. **CLI:** For Jira and GitHub issue workspaces, progress notes, AI context, and provider sync
2. **Desktop:** For visual kanban thinkers

**Key Benefits:**
- Humans and AI agents work from the same story record
- Progress notes preserve observations, decisions, evidence, blockers, and next steps
- Jira and GitHub remain stakeholder-visible while teams work locally
- Git-friendly local history for issue changes
- Shared context reduces handoff risk