Add FlowBoard use case: AI Agent Project Dashboard#133
Open
rasimme wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
A new use case for FlowBoard — a local-first multi-project workspace for OpenClaw and external coding agents (Claude Code, Codex, Cursor).
Two core value props:
1. Knowledge Layer — persistent project context with lazy loading. Activate a project and your agent gets goals, decisions, specs, and current task state without re-explaining anything. Switch between projects, pick up exactly where you left off.
2. Spec-Driven Development from sticky notes — jot a rough idea on the Idea Canvas, one click runs the Specify workflow (ANALYZE → CLARIFY → GENERATE) which asks clarifying questions and turns it into a proper spec with acceptance criteria. The spec lands on an agent-native Kanban board, ready for multi-agent implementation.
Everything runs local, event-sourced in SQLite — no SaaS, no account.
Checklist