@qball-inc/the-bulwark 1.2.0 → 1.3.0

package/skills/pipeline-templates/SKILL.md

@@ -3,6 +3,9 @@ name: pipeline-templates
 description: 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.
 when_to_use: Loaded by the Stop hook (`suggest-pipeline-stop.sh`) when uncovered code/test/script changes accumulate this turn — provides the canonical F# pipe definitions the orchestrator follows when responding to the hook's `decision: block` reason text. Also loadable directly when the orchestrator needs to consult a pipeline definition (e.g., before running Code Review, Test Audit, Fix Validation, New Feature, or Research & Planning workflows).
 user-invocable: false
+allowed-tools:
+  - Read
+  - Skill
 version: 1.0.2
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/plan-creation/SKILL.md

@@ -6,6 +6,16 @@ user-invocable: true
 argument-hint: "<topic, filepath, or directory> [--doc <path>] [--research <synthesis-file>]"
 skills:
   - subagent-prompting
+allowed-tools:
+  - AskUserQuestion
+  - Bash
+  - Edit
+  - Glob
+  - Grep
+  - Read
+  - Skill
+  - Task
+  - Write
 version: 1.0.2
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/plan-to-tasks/SKILL.md

@@ -6,6 +6,14 @@ user-invocable: true
 argument-hint: "<path-to-plan_v{N}.md>"
 skills:
   - subagent-prompting
+allowed-tools:
+  - AskUserQuestion
+  - Edit
+  - Glob
+  - Read
+  - Skill
+  - Task
+  - Write
 version: 1.0.0
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/product-ideation/SKILL.md

@@ -5,6 +5,12 @@ user-invocable: true
 argument-hint: "<idea-description> | --doc <path-to-idea-file>"
 skills:
   - subagent-prompting
+allowed-tools:
+  - AskUserQuestion
+  - Read
+  - Skill
+  - Task
+  - Write
 version: 1.0.0
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/session-handoff/SKILL.md

@@ -2,6 +2,10 @@
 name: session-handoff
 description: 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 next steps.
 user-invocable: true
+allowed-tools:
+  - AskUserQuestion
+  - Read
+  - Write
 version: 1.0.0
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/setup-lsp/SKILL.md

@@ -3,6 +3,12 @@ name: setup-lsp
 description: Configures Language Server Protocol integration for Claude Code projects. Use when setting up LSP servers, verifying post-restart initialization, or troubleshooting broken LSP configurations.
 user-invocable: true
 argument-hint: "[--lang <languages>] [--verify | --troubleshoot]"
+allowed-tools:
+  - AskUserQuestion
+  - Bash
+  - Edit
+  - Read
+  - Write
 version: 1.0.0
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/spec-drift-check/SKILL.md

@@ -6,12 +6,15 @@ argument-hint: "<spec-path> [<additional-context>]"
 arguments: spec_path
 user-invocable: true
 allowed-tools:
+  - AskUserQuestion
   - Bash
-  - Read
-  - Grep
   - Glob
+  - Grep
+  - Read
   - Write
-version: 1.0.0
+disallowed-tools:
+  - Edit
+version: 1.0.1
 author: "Ashay Kubal @ Qball Inc."
 ---
 
@@ -37,7 +40,7 @@ Audits a Work Package brief (or any spec document) for drift against the current
 - Test audit (use `test-audit`)
 - Debugging issues (use `issue-debugging`)
 
-**This skill is READ-ONLY with respect to the subject spec.** It does NOT modify the input brief or any code referenced by it. The skill DOES write its own outputs — verification log under `$PROJECT_DIR/logs/spec-verify-*.md` and diagnostic YAML under `$PROJECT_DIR/logs/diagnostics/` — those are not "modifications" of the subject. To FIX issues found in the subject spec, the user invokes a separate skill (manual edits, `fix-bug`, or an implementer agent). The skill's value is the audit + adjusted plan, not the fix. The frontmatter excludes `Edit` to prevent accidental subject-spec modification at the permission layer.
+**This skill is READ-ONLY with respect to the subject spec.** It does NOT modify the input brief or any code referenced by it. The skill DOES write its own outputs — verification log under `$PROJECT_DIR/logs/spec-verify-*.md` and diagnostic YAML under `$PROJECT_DIR/logs/diagnostics/` — those are not "modifications" of the subject. To FIX issues found in the subject spec, the user invokes a separate skill (manual edits, `fix-bug`, or an implementer agent). The skill's value is the audit + adjusted plan, not the fix. The frontmatter lists `Edit` under `disallowed-tools`, which removes it from the available tool pool while the skill runs, preventing accidental subject-spec modification at the permission layer.
 
 This skill follows the **Reviewer** archetype with the `standalone`, `multi-source`, and `pipeline-stage` sub-patterns. It runs in **Main Context Orchestration** (no sub-agent fork) by deliberate design — the verifier needs to read across the full claimed scope and the orchestrator must absorb the verdict directly to make scope-expansion decisions.
 
@@ -90,7 +93,7 @@ This skill is a read-only Reviewer using Main Context Orchestration. The subject
 - [ ] **Stage 5 — Log**: Verification log written to `$PROJECT_DIR/logs/spec-verify-{session}-{topic}.md` (per references/step-5-log-template.md)
 - [ ] **Stage 6 — Decide**: Verdict emitted (PROCEED / PROCEED_ADJUSTED / STOP_USER_APPROVAL) per finding mix (references/step-6-decision-matrix.md)
 - [ ] **Stage 7 — Bind**: Verified plan SUPERSEDES original spec for rest of WP
-- [ ] **READ-ONLY enforced (subject spec)**: Subject spec MUST NOT be modified at any point during review. Skill outputs (verification log + diagnostic YAML) are NOT modifications of the subject — those are deliverables the skill writes to `$PROJECT_DIR/logs/`. `Edit` is intentionally excluded from `allowed-tools` to enforce subject-read-only at the permission layer
+- [ ] **READ-ONLY enforced (subject spec)**: Subject spec MUST NOT be modified at any point during review. Skill outputs (verification log + diagnostic YAML) are NOT modifications of the subject — those are deliverables the skill writes to `$PROJECT_DIR/logs/`. `Edit` is listed under `disallowed-tools` (and absent from `allowed-tools`) to enforce subject-read-only at the permission layer
 - [ ] **Main Context Orchestration**: Do NOT spawn sub-agents for the verification work — verifier needs full claimed scope; orchestrator needs verdict directly
 - [ ] **Diagnostics**: Diagnostic YAML written to `$PROJECT_DIR/logs/diagnostics/spec-drift-check-{YYYYMMDD-HHMMSS}.yaml`
 - [ ] **Findings + verdict presented to user via AskUserQuestion if STOP_USER_APPROVAL**

package/skills/subagent-output-templating/SKILL.md

@@ -2,6 +2,8 @@
 name: subagent-output-templating
 description: 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.
 user-invocable: false
+allowed-tools:
+  - Write
 version: 1.0.0
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/subagent-prompting/SKILL.md

@@ -2,6 +2,8 @@
 name: subagent-prompting
 description: 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.
 user-invocable: false
+allowed-tools:
+  - Write
 version: 1.0.0
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/test-audit/SKILL.md

@@ -9,6 +9,16 @@ skills:
   - assertion-patterns
   - component-patterns
   - bug-magnet-data
+allowed-tools:
+  - AskUserQuestion
+  - Bash
+  - Edit
+  - Glob
+  - Grep
+  - Read
+  - Skill
+  - Task
+  - Write
 version: 1.1.0
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/test-classification/SKILL.md

@@ -2,6 +2,11 @@
 name: test-classification
 description: Prompt template for test classification stage in Test Audit pipeline
 user-invocable: false
+allowed-tools:
+  - Glob
+  - Grep
+  - Read
+  - Write
 version: 1.0.1
 author: "Ashay Kubal @ Qball Inc."
 ---

package/skills/test-fixture-creation/SKILL.md

@@ -2,6 +2,12 @@
 name: test-fixture-creation
 description: 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.
 user-invocable: false
+allowed-tools:
+  - Bash
+  - Edit
+  - Glob
+  - Read
+  - Write
 version: 1.0.0
 author: "Ashay Kubal @ Qball Inc."
 ---