@stilero/bankan 1.0.16 → 1.0.18

package/README.md

@@ -5,7 +5,7 @@
 # Ban Kan
 
 <p align="center">
-<strong>Run AI coding agents like a Kanban board.</strong>
+<strong>Handle 10+ AI coding agents without losing control.</strong>
 </p>
 
 <p align="center">
@@ -20,6 +20,10 @@ Plan → Implement → Review → Pull Request
 Bring order to parallel AI development without leaving your local workflow.
 </p>
 
+<p align="center">
+  <img src="https://raw.githubusercontent.com/stilero/bankan/HEAD/docs/images/workflow/taskflow_animated.gif" alt="Ban Kan workflow showing planning, implementation, and review progressing across the board" width="1200" />
+</p>
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/stilero/bankan/HEAD/docs/images/bankan_screenshot.png" alt="Ban Kan dashboard showing backlog, planning, implementation, review, and done columns" width="1200" />
 </p>
@@ -66,6 +70,8 @@ npm run dev
 
 Ban Kan starts a local server, opens your browser automatically, and serves the dashboard from the same process.
 
+Contributor workflow, TDD expectations, pull request testing guidance, and verification commands live in [CONTRIBUTING.md](./CONTRIBUTING.md).
+
 ---
 
 ## Requirements
@@ -83,6 +89,14 @@ Linux: build-essential
 
 ---
 
+### Big heads up
+Ban Kan is in early development.
+
+The core workflow works, but bugs and rough edges are expected.
+Feedback is extremely valuable at this stage.
+
+---
+
 ## Quick Start
 
 1. Launch Ban Kan
@@ -131,19 +145,16 @@ All in one dashboard.
 
 ## Why Ban Kan Exists
 
-Most AI coding workflows eventually break down in the same way:
+When developers levels up running multiple AI coding agents they often end up juggling multiple terminals:
 
-- one giant prompt tries to do planning, coding, and review
-- context grows and token usage explodes
-- agents overwrite each other’s work
-- there is no clear review stage
-- parallel development becomes chaos
+- Agent 1 planning a feature
+- Agent 2 implementing code
+- Agent 3 reviewing changes
+- Agent 4 generating tests
 
-Ban Kan fixes this with a model developers already understand:
+Keeping track of everything quickly becomes overwhelming.
 
-**a Kanban board with specialized AI agents.**
-
-Each stage has a clear responsibility, and tasks move forward only when the previous step succeeds.
+In practice most developers struggle to manage more than 3–4 agents at once.
 
 <table>
   <tr>
@@ -164,6 +175,12 @@ Each stage has a clear responsibility, and tasks move forward only when the prev
   </tr>
 </table>
 
+Ban Kan provides a control center that lets you coordinate 10+ agents simultaneously with full visibility of tasks, stages and activity.
+
+**a Kanban board with specialized AI agents.**
+
+Each stage has a clear responsibility, and tasks move forward only when the previous step succeeds.
+
 ---
 
 ## Built for Agile Development
@@ -342,6 +359,8 @@ Useful scripts:
 
 - `npm run build` – build client bundle
 - `npm run dev` – run server + Vite client
+- `npm run lint` – run ESLint across the repo
+- `npm run lint:fix` – apply safe ESLint autofixes
 - `npm run setup` – interactive setup wizard for local runtime config
 - `npm run install:all` – install all dependencies
 

package/bin/bankan.js

@@ -42,7 +42,7 @@ function parseArgs(argv) {
 }
 
 function printHelp() {
-  process.stdout.write(`Ban Kan\n\nUsage:\n  bankan [--port <number>] [--no-open]\n`);
+  process.stdout.write('Ban Kan\n\nUsage:\n  bankan [--port <number>] [--no-open]\n');
 }
 
 function isPortAvailable(port, host) {