bc-harness

Plugin bc-harness from marketplace beer-and-code in beerandcodeteam/beer-and-code-harness. Commands read from the repo's manifest — 1 month ago.

Slash commands (7)

• /bc-harness:ai-context

  Generate or refresh the canonical AGENTS context tree (AGENTS.md, CLAUDE.md, docs/agents/*.md) from the implemented code. Idempotent upsert — safe to re-run; updates only what drifted. Documents reality only; never reads .spec.

• /bc-harness:init

  Show the status of the init spec chain (.spec/init/*) — present, absent, or stale — and run the next init:* command in the chain. Writes nothing itself; all authoring lives in the invoked init:* commands.

• /bc-harness:init:database-schema

  Read the project description and user stories, then derive a suggested database schema in DBML at .spec/init/database-schema.md

• /bc-harness:init:project-description

  Interview the developer, discover the stack, and produce a structured project description at .spec/init/project-description.md

• /bc-harness:init:project-phases

  Read the project description, user stories, database schema, and any design specs, then plan the build into numbered, agent-ready phases with tasks, acceptance criteria, and feature tests at .spec/init/project-phases.md

• /bc-harness:init:user-stories

  Read the project description and derive structured, testable user stories at .spec/init/user-stories.md

• /bc-harness:plan

  Planning pipeline — produces a formal SPEC.md (GEARS RIGID/FLEXIBLE), resolved clarifications, PLAN.md, and optional contracts from a developer-provided description. Writes only under .spec/features/[slug]/; never writes application code.

Subagents (6)

• ai-context-core

  Writer agent for the /ai-context pipeline. Generates or refreshes AGENTS.md and CLAUDE.md in the target repo from the inspector digest. Idempotent — diffs against on-disk bytes, writes only when content changed, respects the ownership contract. Use only as step 4 of /ai-context.

• ai-context-docs

  Writer agent for the /ai-context pipeline. Generates or refreshes the 8 docs/agents/*.md files describing the implemented code as it is (AS IS only — no prescriptive layers). Idempotent — diffs against on-disk bytes, writes only when content changed, respects the ownership contract. Use only as step

• ai-context-inspector

  Read-only repo inspector for the /ai-context pipeline. Sweeps the implemented code (never .spec) and returns a structured digest — stack, commands, layout, signals, artifact ownership — that the writer agents consume verbatim. Use only as step 3 of /ai-context.

• clarifier

  Adversarial requirements QA for the /plan pipeline (step 6). Two modes — analyze (find ambiguities, gaps, contradictions in SPEC.md and return prioritized questions) and resolve (apply developer answers in-place, increment version). Never talks to the developer directly; the router owns the conversa

• planner

  Read-only planning lead for the /plan pipeline (step 7). Produces PLAN.md — architecture-aware task decomposition with dependency phases, risks, validation criteria — plus PHASES.md (ralph.sh-executable view) and conditionally formal contracts (OpenAPI/gRPC/AsyncAPI) from SPEC RIGID. Use only as ste

• specifier

  Requirements engineer for the /plan pipeline (step 5). Transforms a confirmed developer description + ACs into a formal SPEC.md with GEARS syntax, RIGID/FLEXIBLE sections, AS IS / TO BE diagrams, and binary acceptance criteria. Use only as step 5 of /plan.

Hooks (1)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/scripts/sail-guard.sh"