bit

Plugin bit in B4Dmonkey/bit-pro. Commands read from the repo's manifest — 13 days ago.

Skills (10)

• bit_analyze

  Do the deep codebase research a track needs before it is scoped or re-scoped, and leave the findings as research notes through the `mcp__bit__research_*` tools. Use whenever the user says "analyze", "/bit:analyze BIT-N", "research this track", "deep dive before scoping", "dig into the code for this"

• bit_check

  Post-implementation audit that reviews completed work against the plan, PR feedback, and code quality signals. Produces a structured findings list for the retro skill and routes code-change items back through bit_scope → bit_plan → bit_do. Use this skill whenever the user says "bit_check", "check th

• bit_commit

  Commit one bar's work after asking the operator, then record the commit's full hash and branch on the bar and mark it `done`. Use whenever the user says "commit this bar", "commit BIT-N.M", or `/bit:commit`, and whenever bit_do's or theCreator's close-out reaches the commit. It reads the commit mess

• bit_complete

  Complete one or more whole tracks after their work has landed (pushed or merged) — check where the work landed with `mcp__bit__task_landing`, record the landing commit, mark everything done and file the track and its bars as completed through `mcp__bit__task_complete`, so the work actually leaves th

• bit_do

  Execute an existing implementation plan one step at a time, stopping after each step for the user to verify before continuing. Use whenever the user says "implement the plan", "continue our implementation", "let's build the next step", "do the next step", "pick up where we left off", or otherwise wa

• bit_feedback

  Record a correction that landed mid-cycle as a feedback note against the track, so the gap between what the plan said and what the work actually required is captured as evidence instead of being lost. Use whenever the user says "capture that", "record that", "note that for the retro", "add a feedbac

• bit_learn

  Reads the proposals bit_retro stored from every project, through `mcp__bit__retro_list` and `mcp__bit__retro_read`, and for each proposal either drafts the matching bit-pro skill edit via skill-creator, hands a real code/CLI change off to bit_scope to be planned properly, or says plainly that neithe

• bit_plan

  Create or refine an implementation plan for a large task — bug fix, refactor, or new feature. Use when the user says "make a plan", "let's plan this out", "let's revise the plan", names a scope track to plan, or describes a change that is too large to implement in one session. Also triggers on casua

• bit_retro

  Reads across the current project's feedback notes — the evidence bit_feedback records, listed and read through `mcp__bit__feedback_list` and `mcp__bit__feedback_read` — to diagnose what the bit_scope/bit_plan/bit_do/bit_check/bit_feedback process itself failed to settle, and turns any recurring, pip

• bit_scope

  Create or refine a high-level scope (an RFC-style overview) for a feature or change BEFORE any detailed planning. Use this first — whenever the user wants to frame WHAT is changing and WHY at a high level, sketch the shape of a feature request, decide the order of delivery, or surface risks and unkn

Subagents (6)

• analyst

  Researches one topic of a track for bit:analyze and writes that topic's research note. The bit:analyze coordinator dispatches it by `subagent_type: bit:analyst` with no `model` param, one per topic, in parallel. It checks the topic's assumptions and Touches pointers against the code, writes exactly

• bot

  General-purpose assistant for a project tracked by the bit pipeline. Knows the project's `mcp__bit__*` task tools — tracks, bars, verses, feedback notes — so a fresh session can act on requests like "mark BIT-24.2 as done", "what's left on BIT-23", or "add a bar for the migration" without rediscover

• planner

  Writes one approved track's bars by following bit:plan. theRuler dispatches it by `subagent_type: bit:planner` with no `model` param, passing the track ID, the operator's reply verbatim, and analysts' summaries when research answered its earlier questions. It returns the bar IDs and titles it wrote

• scout

  Creates or refines one track's scope by following bit:scope. theRuler dispatches it by `subagent_type: bit:scout` with no `model` param, passing the track ID, the analysts' short summaries, and the operator's reply verbatim. It writes the scope into the track body and returns what changed and how ma

• theCreator

  Executes one bar of a bit plan and lands it. Runs the bit:do skill exactly as written, whose close-out commits through bit:commit once the operator says yes, then pushes that commit if the repo has a remote. Every commit waits for the operator: in a headless run (`-p`, `--bg`) it stops at the ask an

• theRuler

  The operator's entry point for planning new work in a project tracked by the bit pipeline. The operator describes the work; theRuler creates a stub track, runs bit:analyze's coordinator itself, dispatching one bit:analyst per topic for deep research, dispatches bit:scout on top of that research, re-

Hooks (2)

• Stop

  bp receipt

• SubagentStop

  bp receipt