agentleFS
OpenCovenOpenCoven/coven/skills/board/SKILL.md

board

Skill75 starsChanged 4 months agoMITView on GitHub

Read and write the workspace BOARD.md (shared task board for agents + Val). Wraps `bin/board`, a small Python CLI that preserves the markdown schema and appends to the activity log automatically. Use this whenever an agent proposes, claims, or finishes work that should be visible to the rest of the roster.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use validate and plan.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the bin/board CLI instead of editing the file directly.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BOARD — shared task board

BOARD.md lives at the workspace root. Every active agent (nova, kitty, cody, pi, codex) and Val read and write to it. The activity log at the bottom is append-only — never rewrite it.

Use the bin/board CLI instead of editing the file directly. It preserves the schema, restamps timestamps, and writes a matching activity-log row for every mutation.

When to use

  • Proposing a new task → board add
  • Picking up someone else's task → board claim
  • Finishing work that's on the board → board done
  • Checking what's active before starting work → board list
  • Auditing recent agent activity → board log

When NOT to use

  • One-off TODOs that only matter to your current session → use the conversation's todo tool, not BOARD.md
  • Long-form reflection / dream entries → DREAMS.md
  • Repo-specific implementation plans → plans/{org}/{repo}/<file>.md

Commands

# show one section (or all)
board list
board list today

# add a task to a section
board add today "Move demo script to plans/" --agent nova --ctx "It's at workspace root after demo."

# reassign a task's "by" agent
board claim "demo script" --agent kitty

# flip checkbox to done, move to "Done this week", log it
board done "demo script" --agent kitty

# tail the activity log (default 10 rows, newest first)
board log
board log -n 30

Agent identity

The --agent flag wins. If absent, the CLI reads $OPENCLAW_AGENT. If that's also unset, it defaults to nova. Anything outside the roster (nova, kitty, cody, pi, codex, val) is rejected. Fishy retired on 2026-04-28 and should not be used for new board entries.

Set the env var once per agent session so every command stamps correctly:

export OPENCLAW_AGENT=cody
board add today "Run a competitive scan" --ctx "5 sources, summarize in DREAMS"

Title matching for claim / done

Pass any case-insensitive substring of the task title. If the substring matches more than one task, the CLI lists candidates and exits non-zero — narrow the query and retry.

board done "skills"
# error: 'skills' matches 2 tasks:
#   - Commit new skills under `skills/` (pr-agent, prompt-engineer, …)
#   - TinyFish skills scaffolded — search / fetch / browser / agent-run

board done "TinyFish skills"   # unique

Concurrency

Each write takes an flock exclusive lock on BOARD.md. Two agents running board add simultaneously serialize cleanly; humans editing in their text editor bypass the lock and we'll eat the merge conflict if it happens.

File location override

The CLI walks up from $PWD looking for BOARD.md. To target a different file (e.g. for testing), set BOARD_PATH:

BOARD_PATH=/tmp/BOARD-fixture.md board list

See also

  • BOARD.md — the live workspace board (with embedded schema docstring)
  • mockups/board.html — four-view design prototype (Notebook / Console / Whiteboard / Diary)
  • plans/openclaw/openclaw/knotch-board-plan.md — feature plan, schema spec, open questions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.