Repository navigation
feat(board): Owner board — live page of asks, peers, and work in flight - #21
Merged
Merged
Conversation
- templates/board.html: claude.ai artifact page reading a db (asks, peers, work, meta); project values in meta/config - /dev-team:board: publish, seed from status.md, record the Owner board line; bootstrap offers it - workflow/board.md: schema and rules (same turn as status.md, asks deleted when answered, pre-authorized writes) - bin/board-drift: token-free check of work rows against GitHub PR state - tests/board.sh: drift against a fake gh; template rendered with sample data in headless Chrome - README: board section with light/dark screenshots of made-up sample data Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… queued rows Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Second of three PRs from feedback on running 9 peers with one coordinator: the Owner board. With that many roles, the coordinator's chat moves too fast to follow, and the workspace markdown is written for agents. The board is the Owner's view.
What changes
templates/board.html: a private claude.ai artifact page that reads its own database. It has three sections: "Needs you" (questions and approvals), "Who's on what" (one card per role) and "Work" (rows grouped by initiative, with ticket, PR, state and next step). Project values (how it names the Owner, ticket link base, repo) live in ameta/configrecord, not in the HTML./dev-team:boardpublishes the page, seeds it fromstatus.md, and records an**Owner board:** <url>line in the project. Running it again refreshes the page in place and keeps the data. Bootstrap now offers it.workflow/board.mdholds the schema and the rules:status.md;handoffs.md).bin/board-driftchecks the board's work rows against GitHub PR state (merged, failed check, draft vs. ready) without using tokens. Rows are read viaArtifactData listwithout_dir, so reading costs almost nothing.examples/board/sample.json).The Orca worktree-card board (
Board: on) stays as the lighter, Orca-only option. The two can run together.Testing
tests/board.sh(22 checks, run by CI on Linux and macOS):board-driftagainst a fakegh: each drift rule (including a missing PR, and a ready PR on aplanningorqueuedrow), rows that stay quiet, the per-row repo override, nested files, and exit codes.The README screenshots come from that same preview path (
tests/board-preview.py).claude plugin validate .shows the same warnings as main. Not exercised: publishing through the real Artifact and ArtifactData tools, which the/dev-team:boardcommand drives in a consuming project.🤖 Generated with Claude Code