the-bulwark

Plugin the-bulwark in QBall-Inc/the-bulwark. Commands read from the repo's manifest — 1 month ago.

Skills (30)

• anthropic-validator

  Validates Claude Code assets (skills, hooks, agents, commands, MCP servers, plugins) against official Anthropic standards. Fetches latest docs dynamically and produces structured validation reports.

• assertion-patterns

  Real output verification vs mock calls. Use when transforming T1-T4 violating tests to verify observable behavior.

• bug-magnet-data

  Curated edge case test data for boundary testing, verification scripts, and test generation. Provides pre-curated reference data organized by data type with context-specific loading guidance.

• bulwark-brainstorm

  Role-based brainstorming with dual modes: --scoped (sequential Task tool, 5 roles) and --exploratory (Agent Teams peer debate, 4 roles). Use for feasibility assessment and idea validation.

• bulwark-research

  Structured multi-viewpoint research using 5 parallel Sonnet sub-agents. Use when deep research is needed on a complex topic before implementation planning.

• bulwark-scaffold

  Initialize Bulwark infrastructure in a project: language-aware Justfile (8 langs), bun + eval-framework toolchain, logs/ subdirectories, and optional hooks.

• bulwark-statusline

  Configure the Bulwark status line for Claude Code. Supports init, preset switching, and customization.

• bulwark-verify

  Generate runnable verification scripts for components. Orchestrates assertion-patterns and component-patterns to produce executable scripts.

• code-review

  Comprehensive code review with distinct aspect based sections. Use when reviewing code, checking for security issues, finding type safety problems, auditing code quality, or when user asks to review code, PRs or changes. Three-phase workflow runs static tools, LLM judgment, and writes diagnostic log

• component-patterns

  Per-component-type verification approaches. Use when generating verification scripts for different component types.

• continuous-feedback

  Identifies improvement targets from accumulated session learnings and proposes concrete skill/agent modifications. General-purpose pipeline for any Claude Code project.

• create-skill

  Generates Claude Code skills from requirements using adaptive interview, complexity classification, and iterative validation. Use when creating new skills, scaffolding skill structure, or generating skills with sub-agent orchestration.

• create-subagent

  Generates single-purpose Claude Code sub-agents for use via the Task tool. Use when creating dedicated sub-agents, scaffolding agent definitions, or generating agents with diagnostics and permissions setup.

• fix-bug

  Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.

• governance-protocol

  Session governance protocol injected at startup via SessionStart hook

• init

  Initialize, verify, or update Bulwark governance in a project. Sets up CLAUDE.md, rules.md, and optional tooling (statusline, LSP, scaffold). --update reviews canonical template changes interactively per-section.

• issue-debugging

  Systematic methodology for issue debugging including root cause analysis, impact mapping, tiered validation plans, and confidence assessment. Use when analyzing bugs, fixing issues, or validating fixes.

• mock-detection

  Deep mock appropriateness analysis for Test Audit pipeline

• pipeline-templates

  Pre-defined F# pipe workflows for multi-agent orchestration. Provides code review, fix validation, test audit, new feature, research & planning, and test execution pipelines. Triggered via PostToolUse hook after significant code changes.

• plan-creation

  Create structured implementation plans via a 4-role scrum team (Product Owner, Architect, Eng/Delivery Lead, QA/Critic) with optional Agent Teams peer debate mode.

• plan-to-tasks

  Transform a plan_creation plan_v{N}.md into a structured tasks.yaml + per-WP workpackages/*.yaml using parallel Sonnet sub-agents. Use after plan-creation finishes when you need execution-friendly task structure.

• product-ideation

  Evaluates product ideas through a six-agent research pipeline producing BUY/HOLD/SELL recommendations backed by market analysis, competitive intelligence, and segment targeting. Use when assessing product viability, researching markets for new ideas, or deciding whether to pursue a product concept.

• session-handoff

  Create consistent session handoff documents for context transfer between sessions. Use when closing a session, reaching 75% token consumption, or when user requests handoff. Ensures proper YAML headers for metrics collection, LF line endings, and complete documentation of progress, decisions, and ne

• setup-lsp

  Configures Language Server Protocol integration for Claude Code projects. Use when setting up LSP servers, verifying post-restart initialization, or troubleshooting broken LSP configurations.

• spec-drift-check

  Audits a WP brief for drift against current code — extracts claims, verifies each, emits PROCEED/STOP verdict. Use when starting a new WP, before consuming a spec as binding, or when a doc references paths/lines/functions.

• subagent-output-templating

  Template for structured sub-agent output including YAML log format, task completion reports (WHY/WHAT/TRADE-OFFS/RISKS), and summary constraints. Use when defining how sub-agents should report results.

• subagent-prompting

  Template for structured sub-agent invocation using 4-part prompting (GOAL/CONSTRAINTS/CONTEXT/OUTPUT) and F# pipeline notation. Use when orchestrating sub-agents or designing multi-agent workflows.

• test-audit

  Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fai

• test-classification

  Prompt template for test classification stage in Test Audit pipeline

• test-fixture-creation

  Guidelines for creating unbiased test fixtures that integrate with project infrastructure. Use when creating fixtures for manual testing, setting up E2E test scenarios, or building code samples with deliberate issues for LLM review. Ensures fixtures work with hook automation and pass Phase 1 checks.

Subagents (15)

• bulwark-fix-validator

  Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.

• bulwark-implementer

  Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.

• bulwark-issue-analyzer

  Analyzes issues to identify root cause, map impact, and produce debug report with tiered validation plan. Supports both production code bugs and test code issues.

• bulwark-standards-reviewer

  Critical analysis of Claude Code assets against official standards. Produces severity-rated findings with remediation suggestions. Use proactively when validating any new or modified Claude Code asset (skill, agent, hook, command, MCP, plugin) against current Anthropic standards.

• plan-creation-architect

  Technical architect for implementation plan creation. Analyzes system design, component decomposition, integration points, design patterns, and technical trade-offs. Reads Product Owner output and optional research synthesis. Use when architectural analysis is needed for a new feature, system, or im

• plan-creation-eng-lead

  Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.

• plan-creation-po

  Product Owner for the plan-creation pipeline. Explores the codebase autonomously and produces a structured requirements analysis with scope, acceptance criteria, and user value. Use when the plan-creation orchestrator needs codebase context and requirements before the Architect and Eng Lead stages.

• plan-creation-qa-critic

  QA / Critic for the plan-creation pipeline. Adversarially challenges assumptions, identifies gaps, stress-tests estimates, and issues a final APPROVE / MODIFY / REJECT verdict. Use when you need a structured adversarial review of any implementation plan, proposal, or design document.

• product-ideation-competitive-analyzer

  Profiles direct and indirect competitors, analyzes market positioning and pricing, investigates failed competitors, and identifies market gaps using Porter's Five Forces. Reads market research output from logs/. Use when the orchestrator needs competitive intelligence built on market research.

• product-ideation-idea-validator

  Assesses product idea merit across feasibility, timing, uniqueness, and problem-solution fit. Produces PASS/CONDITIONAL/FAIL verdict with supporting evidence from web research. Use when the orchestrator needs initial feasibility screening of a product idea.

• product-ideation-market-researcher

  Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.

• product-ideation-pattern-documenter

  Analyzes competitive data to document success/failure patterns, competitor trajectories, and opportunity gaps. Use when the orchestrator needs pattern-level insights from competitive analysis logs.

• product-ideation-segment-analyzer

  Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.

• product-ideation-strategist

  Synthesizes all pipeline research outputs into a definitive BUY/HOLD/SELL recommendation with confidence level, strategic rationale, and actionable next steps using the final-report template. Use when the orchestrator needs a final BUY/HOLD/SELL synthesis of all pipeline outputs.

• statusline-setup

  Configures the user's Claude Code status line setting. Handles settings.json updates and config file placement.

Hooks (9)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/bulwark-permission-hook.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/enforce-quality.sh

• SubagentStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/track-pipeline-start.sh

• SubagentStop

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/track-pipeline-stop.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/suggest-pipeline-stop.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/inject-protocol.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/cleanup-stale.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/cleanup-review-registry.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/check-template-drift.sh

Similar plugins