Structure development work into sessions with plans, progress tracking, and resumable context.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "aidflow" yet — see the docs or source repo.
Create a session-based development plan for adding a user permission system to an existing web app. Break it into phases and list each session’s goal, dependencies, acceptance criteria, and estimated time.
A session-organized development plan with phase goals, task breakdowns, and acceptance criteria.
Update this development session based on current progress: backend APIs are complete, the frontend permissions page is 60% done, and testing has not started. Summarize completed work, remaining tasks, blockers, and generate a context summary for the next session.
An updated progress log, blocker list, and a context summary for the next session.
Archive the completed development sessions for the 'payment module refactor' project. Preserve key decisions, implementation summaries, remaining risks, and follow-up optimization suggestions for future review.
A structured archive that makes historical decisions and project context easy to review later.
Search and navigate Claude Code session history with fork-aware context.
Access Aidoo studio data in Claude for members, classes, bookings, and contracts.
Persist Claude sessions and coordinate multi-agent workflows with tracking tools.
Control Claude Code sessions in tmux with fine-grained orchestration and efficient extraction.
Manage Claude Code sessions with search, rename, split, and cleanup tools.
Give Claude Code persistent memory and semantic context retrieval across sessions.