← ClaudeAtlas

featureboardinglisted

Board substantive dev requests on FeatureBoard automatically and churn them with parallel sub-agents — with verified dispatch, heartbeat liveness, and per-completion merging. Use when the user asks to build, fix, ship, implement, refactor, "work on", or "swarm" anything non-trivial in a project — they should NOT have to say "put it on the board".
valentil/featureboard-mcp · ★ 2 · AI & Automation · score 60
Install: claude install-skill valentil/featureboard-mcp
# Featureboarding Run the FeatureBoard churn loop end to end: board the work, then work the board — and PROVE the work is moving. Four failure modes this skill exists to prevent (all observed in real runs): lanes narrated as dispatched but never spawned; finished work sitting uncommitted in worktrees; sub-agents ending early to "ask for guidance" nobody can hear; and a blind agent monitor because nobody heartbeats. ## 0. Pre-flight sweep — before dispatching anything - `get_agent_monitor` (stallMinutes: 15). Any ticket already In Progress and stalled with no live agent from THIS session behind it is a zombie from a dead run: reset it to Todo (`set_status`, note why via `log_work`) so `next_wave` can re-serve it. Zombie In Progress tickets silently shrink every wave. - `list_worktrees`. A worktree branch with commits (or dirty files) not on the main branch is orphaned finished work: review, `commit_feature`, then `cleanup_worktree` before starting new lanes. - Check the work packet's `gitTargets` — code commits and projectpad commits can target DIFFERENT repos. Never assume. ## 0.5 First install — offer "all the way" onboarding If `list_projects` returns no boards (`firstRun: true` on the response), this is a fresh install: BEFORE anything else, offer all-the-way onboarding and explain it in one short paragraph — one brief round of questions (project name, code repo path, git push mode, what they're building first), then the board is created and configured, he