Kanban board makerfrom plain language, free.
/ Example
(01)Prompt: A launch checklist for a mobile app, split into to do, doing and done
kanban
todo[To do]
icon[Final app icon and splash screen]@{ assigned: 'Maya', priority: 'High' }
screens[App Store screenshots]@{ assigned: 'Leo', ticket: 'APP-41' }
privacy[Privacy policy page]@{ assigned: 'Sam', priority: 'Very High' }
press[Press kit and launch post]@{ priority: 'Low' }
doing[Doing]
beta[Fix beta crash reports]@{ assigned: 'Priya', ticket: 'APP-37', priority: 'Very High' }
onboarding[Polish onboarding]@{ assigned: 'Maya', ticket: 'APP-35' }
analytics[Launch analytics]@{ assigned: 'Leo', priority: 'Low' }
review[In review]
purchases[In-app purchases]@{ assigned: 'Priya', ticket: 'APP-30', priority: 'High' }
push[Push notifications]@{ assigned: 'Sam', ticket: 'APP-33' }
done[Done]
testflight[TestFlight beta]
crashes[Crash reporting]
website[Website and domain]
/ Good for
(02)- Sprint snapshots in a README or doc
- Planning a small project
- Showing work in progress in a report
(03)
drop something in
1text, notes, whatever
it turns into a diagram
2usually in a few seconds
tweak it if you want
3export it and move on
/ Other diagram types
(04)- FlowchartSign-up, checkout and approval flows
- Sequence DiagramAPI requests across services
- Class DiagramObject-oriented designs and domain models
- State DiagramOrder and ticket lifecycles
- ER DiagramDatabase schema design
- User JourneyOnboarding and first-run experiences
- Gantt ChartProject and release schedules
- Pie ChartBudget and cost breakdowns
- Git GraphExplaining a branching strategy
- Mind MapBrainstorming and planning
- TimelineProduct and company history
- Requirement DiagramTracing requirements to components
- Quadrant ChartEffort and impact prioritisation
- C4 DiagramSystem context for new team members
- Sankey DiagramBudget and money flows
- XY ChartMonthly sales or sign-ups
- Block DiagramHigh-level system overviews
- Packet DiagramProtocol and file format documentation
- Architecture DiagramCloud infrastructure overviews
- Radar ChartComparing products or frameworks
- TreemapBudgets broken down by department
- Ishikawa DiagramRoot cause analysis after an incident
- Venn DiagramComparing products or roles
- Tree ViewProject folder layouts in a README