bearing-lite

Plugin bearing-lite from marketplace bearing-lite in alphazede/bearing-lite. Commands read from the repo's manifest — 13 days ago.

Skills (16)

• architectural-alignment

  Establish architectural fit and resolve material scope decisions after Intake is confirmed. Use for Architectural Alignment, Scope Definition, missing or stale context, or unresolved intent in an explicitly requested Bearing lifecycle. Do not use for already-settled current context, design, implemen

• bearing-lite

  Coordinate a Bearing lifecycle as Planning or Implementation Orchestrator only when the owner explicitly requests Bearing for that mode. Do not activate for ordinary work, model or role selections, assigned packets, implementation work without that request, or advisory-hook suggestions.

• coordinator

  Coordinate one approved implementation wave only when enabled in the selected profile and assigned that wave. Use for independent packet scheduling and wave evidence integration. Do not use for planning, implementation authorship, cross-wave work, automatic nesting, or independent review.

• implementer

  Implement one approved bounded packet in an exact write set. Continue the same-wave session when identity, authority, route, and generation are unchanged. Use for Implementer, Product Implementer, Test Implementer, implementation, repair, or integration packets. Do not use for orchestration, plannin

• intake

  Verify and propose one target repository and plan directory when repository identity is absent or ambiguous. Use for Intake before Architectural Alignment. Do not use after owner-confirmed fit, for parent-wide exploration, planning decisions, product edits, role routing, or publication.

• integration-engineer

  Author selected integration planning inputs, or perform explicitly requested independent assessment of an integrated candidate. Use the enabled configured planning or execution session only. Do not implement missing behavior, rewrite requirements, write product tests, or activate an undeclared asses

• light-implementer

  Execute one approved light slice exactly as its packet states, verified by the packet's deterministic command. Use for Light Implementer, light, mechanical, scaffold, bind, assemble, regenerate, or runbook packets. Do not use for judgement work, authoring, repair, review, or any decision.

• onboard-bearing

  Guided first-run and later configuration of profiles.json. Use for explicit profile setup or configuration change. Do not use to infer settings, store credentials, or write during ordinary Lifecycles.

• planning-and-design

  Perform final planning/design in the Planning Orchestrator's current session after the selected specialists return. Use for final plan/design and assembly or an authorized planning correction. Do not dispatch a separate author, repeat specialist requirements or SEIT work, or start implementation.

• prompt

  Compose one bounded handoff for an already selected agent role and session. Do not select roles or routes, start a lifecycle, dispatch agents, add reviews, invent budgets, or turn controller procedures into specialist assignments.

• requirements-engineer

  Author requirements and acceptance criteria for selected planning work after scope is settled. Use for Requirements Engineer authorship or an authorized requirements correction. Do not use as an independent quality reviewer, for implementation, V&V authorship, model selection, or publication.

• reviewer

  Independently review one exact stable candidate for introduced actionable defects in a fresh session at the configured cadence boundary. Use for Reviewer, code review, or defect adjudication. Do not use for implementation, automatic review, evidence scoring, user acceptance, author self-review, or u

• scope-definition

  Compatibility name for the scope interview within Architectural Alignment. Use for older Scope Definition requests or reroutes in an explicitly requested Bearing lifecycle. Do not run as a separate stage, agent, or repeated interview.

• scribe

  Transcribe Lifecycle decisions, authority events, ledger snapshots, and profile selections as an event side lane. Use for Scribe. Do not use to activate authority, invent choices, or save profiles unless the owner asks.

• systems-modeler

  Select modeling mode and attach view metadata in the planning wave before design finalization. Use for Systems Modeler planning session. Do not model execution waves or author requirements.

• test-engineer

  Author the SEIT and validation approach as Planning Test Engineer, or perform explicitly requested independent V&V as Assurance Test Engineer. Do not use for implementation, defect review, user acceptance, or undeclared boundaries.

Hooks (8)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/com.anthropic.claude-code/host.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/assurance-dispatch.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/te-host.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/orchestrator-write-lock.cjs"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/com.anthropic.claude-code/host.cjs"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/te-host.cjs"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/git-sync.cjs"

• SubagentStop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/te-host.cjs"

Similar plugins