AI Plans

AI Plans

Track every AI-assisted coding decision in version control

5 followers

AI Plans capture the complete context of AI-assisted development in markdown files. Track requests, implementation strategies, task breakdowns, and issues encountered. Create a searchable history of AI interactions in your repo's /plans/ directory.
AI Plans gallery image
AI Plans gallery image
AI Plans gallery image
AI Plans gallery image
AI Plans gallery image
AI Plans gallery image
Free
Launch Team
Unblocked AI Code Review
Unblocked AI Code Review
High-signal comments based on your team's context
Promoted

What do you think? …

Justin Fuller
AI Plans brings structured documentation to AI-assisted development. As developers increasingly use AI tools like Claude, Copilot, and Cursor, we're losing valuable context about how and why our code was generated. AI Plans are version-controlled markdown files that live in your repository, capturing: βœ… Original developer requests - What you actually asked the AI 🎯 Implementation strategies - The AI's proposed approach πŸ“‹ Task breakdowns - Step-by-step execution plans 🚨 Issues & resolutions - Problems encountered and how they were solved Why it matters: - Knowledge retention: Future developers (or future you) can understand the reasoning behind AI-generated code - Debugging context: When something breaks, see exactly what the AI was trying to accomplish - Team collaboration: Share AI interaction patterns and successful prompting strategies - Audit trail: Track AI involvement in critical code decisions Key Features: πŸ” Searchable history - All plans in /plans/ directory, fully indexed by git πŸ“ Standard format - Consistent structure makes plans easy to read and write πŸ”„ IDE integration - Works with Claude Code, Cursor, and GitHub Copilot ⚑ Zero overhead - Simple markdown files, no dependencies or tools required Who's it for? - Teams using AI pair programming tools - Solo developers wanting to track their AI interactions - Organizations needing documentation for AI-assisted code - Anyone who's ever wondered "why did the AI write it this way?" Get Started: 1. Create a /plans/ directory in your repo 2. Add YYYY-MM-DD-description.md files for each AI session 3. Include: Summary, Request, Plan, TODOs, and Issues 4. Commit alongside your code changes Try it now: Visit https://ai-plans.dev for examples and documentation