balka

Plugin balka from marketplace meteof-skills in meteoFurletov/skills. Commands read from the repo's manifest — 1 month ago.

Skills (2)

• balka-artifacts

  Use when writing or updating an SDLC artefact — intent.md, spec.md, plan.md, a Gherkin .feature file, the facts document or PROPOSALS.md — in a repo carrying .claude/balka.json, and no /balka command was typed. Covers the house rules those artefacts must follow (read the facts document first, link u

• balka-watch-writeback

  Use when a Stage 6 CI drift detection has fired and the diagnosis must be written back as a draft intent.md — normally a headless `claude -p` run started by the balka-watch GitHub Actions workflow, whose prompt carries a band breach, a rolling baseline mean and sigma, and a daily failure-rate series

Slash commands (11)

• /balka:board

  Show the board — every change in this repo, across every worktree, as a kanban with each card's next command. Opens live in the Claude desktop app's Browser pane; prints as markdown anywhere else.

• /balka:build

  Stage 3, Build, second half — implement an accepted plan.md and run the verify commands until they are green, without stopping for anything the plan already settled.

• /balka:deploy

  Stage 5, Deploy — push the branch, open the pull request, let Copilot code review it, address every finding, and print how this change lands. Merging stays with the code owner.

• /balka:init

  Set this repo up for balka — opt-in marker, the facts document, the proposals inbox, starter AGENTS.md block and review policy, and optionally the deploy gate and Stage 6 detector.

• /balka:intent

  Stage 1, Plan — write intent.md for a change: the problem, the outcome and the behaviours in plain words; split a programme into children.

• /balka:plan

  Stage 3, Build, first half — plan the implementation from an accepted spec.md in plan mode, naming the files that change and the scenarios the work proves.

• /balka:reflect

  Reflect — read the proposals inbox, the change directories and the git history, and produce the change list for the next version of the loop, each item routed to the plugin or kept in this project.

• /balka:spec

  Stage 2, Design — turn an accepted intent.md into spec.md, the Gherkin .feature files that are the contract, and their bindings written red.

• /balka:test

  Stage 4, Test — run the verify commands once more in a fresh context, then a verifier that did not write the code checks spec, scenarios, bindings and code against each other. Produces a fix or a stop, never a file.

• /balka:verify

  Fill the verify block in .claude/balka.json — the build, test, lint and scenario commands Build runs until green — by proposing each from the repo and running it once.

• /balka:watch

  Stage 6 — scaffold the CI failure-rate detector into this repo: bands.yaml, the watcher script and a scheduled workflow.

Hooks (4)

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/protect-scenarios.sh" "${CLAUDE_PROJECT_DIR}"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/scenario-commit.sh" "${CLAUDE_PROJECT_DIR}"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/plan-sync.sh" "${CLAUDE_PROJECT_DIR}"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/deploy-gate.sh" "${CLAUDE_PROJECT_DIR}"

Similar plugins