Introduction

Flanner is a comprehensive plan file management system that integrates with Claude Code and other AI assistants through MCP (Model Context Protocol).

What is Flanner?

Flanner helps you manage AI-generated plan files (.md files) with automatic versioning, Git protection, and seamless integration with your development workflow.

Key Features

🤖 MCP Integration

Direct integration with Model Context Protocol exposes plan file management tools to Claude and other AI assistants. Ask Claude to create and manage plans without manual intervention.

📁 Git Protection

Automatically prevents plan files from being committed to git by updating your .gitignore. Keep your plans local while your code stays versioned.

🔖 Smart Identification

YAML frontmatter clearly marks managed plan files with UUIDs, project information, and version numbers for global uniqueness and future cloud compatibility.

📝 Automatic Versioning

Every change to a plan file creates a new version with semantic versioning. Track the evolution of your plans with full history and rollback capabilities.

🌐 Web Interface

Beautiful browser-based UI for viewing, editing, and managing plans. Features markdown rendering with syntax highlighting, version history timeline, and responsive design.

🔗 JIRA Integration

Link plan files to JIRA issues (Epics, Stories, Tasks) to connect your planning documents with project management.

⚙️ CLI Tool

Powerful command-line interface with 25+ commands for project management, plan file operations, JIRA linking, and Claude Code integration.

How It Works

For Developers

• Plan files stored in your project repository (default: .plans/)
• Automatically excluded from git via .gitignore
• Clear identification via YAML frontmatter
• Configurable directory per project
• SQLite database tracks metadata and versions

For Claude/AI Assistants

• Calls get_plan_config() to know where to create files
• Automatic frontmatter generation with UUIDs
• Version management happens transparently
• No need to ask users where files should go

Architecture

Flanner uses a three-tier architecture:

• CLI/Desktop - Flanner CLI with local MCP server
• Backend - FastAPI for authentication, payments, and API keys
• Frontend - Next.js landing page + Flanner web UI

Use Cases

• Architecture Planning - Design system architecture with AI assistance
• API Design - Plan API endpoints and data structures
• Feature Specs - Write detailed feature specifications
• Technical Decisions - Document technical decisions and rationale
• Project Roadmaps - Create and version project roadmaps
• Team Collaboration - Share plans linked to JIRA tickets