strikethroo 3.4.2 → 3.6.0

package/templates/harness/skills/st-execute-task/scripts/validate-plan-blueprint.cjs

@@ -39,7 +39,7 @@ var path4 = __toESM(require("path"));
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-full-workflow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: st-full-workflow
-description: Execute the complete Strikethroo workflow from plan creation through blueprint execution for this repository. Use when the user asks to run the full end-to-end workflow for a work order — discovers the local .ai/strikethroo root, creates a plan, generates atomic tasks, and executes the blueprint, all in a single uninterrupted sequence. Do not use for individual plan creation, task generation, or blueprint execution; use the dedicated skills for those.
+description: Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or execute a blueprint); use the dedicated skill for that stage instead.
 ---
 
 # st-full-workflow
@@ -166,7 +166,9 @@ Each task must be:
 - **Single-purpose** — one clear deliverable.
 - **Atomic** — cannot be meaningfully split further.
 - **Skill-specific** — executable by an agent with 1–2 technical skills.
-- **Verifiable** — has explicit acceptance criteria.
+- **Verifiable** — has explicit acceptance criteria that include at least one
+  concrete, runnable verification step (a command plus its expected output, or
+  another observable signal). Never settle for a vague "works correctly".
 
 Skill assignment (kebab-case, automatically inferred from the task's
 technical requirements):
@@ -266,6 +268,9 @@ Before declaring task generation complete, verify:
 - Task IDs are unique, sequential, and start from the value returned by
   `get-next-task-id.cjs`.
 - Groups are consistent and meaningful.
+- Every task's Acceptance Criteria includes at least one concrete, runnable
+  verification step (command + expected output / observable signal), not a
+  vague "works correctly".
 - Every **explicitly stated** deliverable in the plan is covered.
 - No redundant or overlapping tasks.
 - Minimization applied (20–30% reduction target).
@@ -334,6 +339,7 @@ Read these files in order:
 - `<root>/config/STRIKETHROO.md` — directory conventions and project context.
 - The plan document.
 - The plan's Execution Blueprint section — this defines the phase groupings and task dispatch order.
+- `<root>/config/shared/verification-gate.md` — apply in the phase loop below.
 
 #### 5. Execute phases in order
 
@@ -357,6 +363,8 @@ Maximize parallelism within each phase. Run every task that is ready at the same
 ##### 5c. Phase completion verification
 Ensure every task in the phase has status `completed`. Collect and review all task outputs. Document any issues or exceptions encountered.
 
+Do not accept a subagent's report of success as proof. Apply the evidence gate in `<root>/config/shared/verification-gate.md` before marking the phase complete. Do not mark a phase complete on an unverified claim.
+
 ##### 5d. Phase post-execution
 Read `<root>/config/hooks/POST_PHASE.md` and execute its instructions. Do not proceed to the next phase until this hook succeeds.
 
@@ -368,6 +376,8 @@ Repeat for the next phase until all phases are complete.
 
 Read `<root>/config/hooks/POST_EXECUTION.md` and execute its instructions. If validation fails, halt execution. The plan remains in `plans/` for debugging.
 
+Before declaring execution complete, apply the evidence gate in `<root>/config/shared/verification-gate.md` to the plan's Success Criteria and Self Validation steps.
+
 #### 7. Append execution summary
 
 Append an execution summary section to the plan document using the format described in `<root>/config/templates/EXECUTION_SUMMARY_TEMPLATE.md`. Populate:

package/templates/harness/skills/st-full-workflow/scripts/create-feature-branch.cjs

@@ -54,7 +54,7 @@ var path3 = __toESM(require("path"));
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-full-workflow/scripts/find-strikethroo-root.cjs

@@ -37,7 +37,7 @@ module.exports = __toCommonJS(find_strikethroo_root_exports);
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-full-workflow/scripts/get-next-plan-id.cjs

@@ -37,7 +37,7 @@ module.exports = __toCommonJS(get_next_plan_id_exports);
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-full-workflow/scripts/get-next-task-id.cjs

@@ -41,7 +41,7 @@ var path3 = __toESM(require("path"));
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-full-workflow/scripts/validate-plan-blueprint.cjs

@@ -39,7 +39,7 @@ var path4 = __toESM(require("path"));
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-generate-tasks/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: st-generate-tasks
-description: Generate atomic Markdown tasks for an existing Strikethroo plan in this repository. Use when the user asks to decompose a specific plan ID into tasks — discovers the local .ai/strikethroo root, resolves the plan, runs the project's task-generation hooks, allocates sequential task IDs, and writes one task file per atomic unit conforming to TASK_TEMPLATE.md. Do not use for generic project planning or work outside Strikethroo.
+description: Use when the user asks to decompose, break down, or generate tasks for an existing Strikethroo plan ID in this repository — triggers include generate tasks, break down the plan, decompose plan, create the task blueprint. Do not use to create a new plan, to execute tasks, or for generic project planning outside Strikethroo.
 ---
 
 # st-generate-tasks
@@ -56,6 +56,7 @@ Read these files, in order:
   what tasks must exist.
 - `<root>/config/templates/TASK_TEMPLATE.md` — every task file you emit must
   conform to this template's frontmatter schema and section structure.
+- `<root>/config/shared/anti-rationalization.md` — apply in step 4.
 
 ### 4. Analyze and decompose the plan
 
@@ -85,6 +86,15 @@ Decompose each deliverable into atomic tasks only when genuinely needed.
   not mention.
 - Comprehensive test suites for trivial functionality.
 
+Apply `<root>/config/shared/anti-rationalization.md` to this rationalization table:
+
+| You catch yourself thinking… | The binding rule |
+| --- | --- |
+| "One extra task won't hurt." | It violates the 20–30% minimization target. Every task traces to an **explicitly stated** deliverable or it does not exist. |
+| "This edge case deserves its own task." | Fold it into the task that owns the behavior. Do not split trivially small operations into separate units. |
+| "I'll add a test suite to be safe." | Comprehensive tests for trivial functionality are gold-plating. Follow the test philosophy — meaningful tests only. |
+| "Future extensibility justifies this task." | YAGNI. The plan does not mention it, so it is not a task. |
+
 ### 5. Apply granularity and skill rules
 
 Each task must be:
@@ -92,7 +102,9 @@ Each task must be:
 - **Single-purpose** — one clear deliverable.
 - **Atomic** — cannot be meaningfully split further.
 - **Skill-specific** — executable by an agent with 1–2 technical skills.
-- **Verifiable** — has explicit acceptance criteria.
+- **Verifiable** — has explicit acceptance criteria that include at least one
+  concrete, runnable verification step (a command plus its expected output, or
+  another observable signal). Never settle for a vague "works correctly".
 
 Skill assignment (kebab-case, automatically inferred from the task's
 technical requirements):
@@ -198,6 +210,9 @@ Before declaring task generation complete, verify:
 - Task IDs are unique, sequential, and start from the value returned by
   `get-next-task-id.cjs`.
 - Groups are consistent and meaningful.
+- Every task's Acceptance Criteria includes at least one concrete, runnable
+  verification step (command + expected output / observable signal), not a
+  vague "works correctly".
 - Every **explicitly stated** deliverable in the plan is covered.
 - No redundant or overlapping tasks.
 - Minimization applied (20–30% reduction target).

package/templates/harness/skills/st-generate-tasks/scripts/find-strikethroo-root.cjs

@@ -37,7 +37,7 @@ module.exports = __toCommonJS(find_strikethroo_root_exports);
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-generate-tasks/scripts/get-next-task-id.cjs

@@ -41,7 +41,7 @@ var path3 = __toESM(require("path"));
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-generate-tasks/scripts/validate-plan-blueprint.cjs

@@ -39,7 +39,7 @@ var path4 = __toESM(require("path"));
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-refine-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: st-refine-plan
-description: Refine an existing Strikethroo plan in this repository. Use when the user asks to review, improve, interrogate, or update a specific plan ID — discovers the local .ai/strikethroo root, resolves the plan, runs the project's plan hooks, pressure-tests the document for gaps and contradictions, gathers clarifications interactively or autonomously, and updates the plan in-place while preserving its identity and structure. Do not use for creating new plans or for generic brainstorming outside Strikethroo.
+description: Use when the user asks to review, refine, improve, interrogate, pressure-test, or update an existing Strikethroo plan by plan ID in this repository — triggers include refine plan, improve plan, review plan, red-team the plan, update plan. Do not use to create a new plan, to generate tasks, or for generic brainstorming outside Strikethroo.
 ---
 
 # st-refine-plan
@@ -55,6 +55,7 @@ Read these files, in order:
   before proceeding.
 - `<root>/config/templates/PLAN_TEMPLATE.md` — the structural baseline the
   refined plan must continue to conform to.
+- `<root>/config/shared/clarification-gate.md` — apply in the Clarification Loop.
 
 ### 4. Baseline Review
 
@@ -107,16 +108,19 @@ appropriately.
 Think harder before interrupting the user — only trigger this loop when you
 can cite concrete uncertainties.
 
+Follow the clarification cadence in `<root>/config/shared/clarification-gate.md`.
+
 1. Review the gaps documented in the Baseline Review.
 2. If no gaps remain, stop here and proceed to Stage 6.
-3. Build a clarification packet grouped by theme.
+3. Group the open questions by theme, but ask them one at a time per the
+   cadence above rather than dumping them as a single batch.
 4. Prefill each question with the most plausible answer so the user can
    confirm or deny quickly.
 5. Always include an "Other / open-ended" option to capture nuances you did
    not anticipate.
-6. **STOP AND ASK**: Present the clarification packet to the user. You must
-   halt execution here and await user input. Do not simulate the user's
-   response. Do not proceed to Stage 6 until you have received explicit answers.
+6. **STOP AND ASK**: Put each question to the user and halt execution to await
+   their input. Do not simulate the user's response. Do not proceed to Stage 6
+   until you have received explicit answers and confirmed the resolved scope.
 7. After receiving answers, record them in the Plan Clarifications table.
    If the user cannot answer a question, record it as unresolved with
    mitigation notes so downstream assistants know the risk.

package/templates/harness/skills/st-refine-plan/scripts/find-strikethroo-root.cjs

@@ -37,7 +37,7 @@ module.exports = __toCommonJS(find_strikethroo_root_exports);
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/harness/skills/st-refine-plan/scripts/validate-plan-blueprint.cjs

@@ -39,7 +39,7 @@ var path4 = __toESM(require("path"));
 // src/skill-scripts/shared/root.ts
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
-var EXPECTED_SCHEMA = true ? 1 : 1;
+var EXPECTED_SCHEMA = true ? 2 : 2;
 var isValidStrikethrooRoot = (strikethrooPath) => {
   try {
     if (!fs.existsSync(strikethrooPath)) return false;

package/templates/strikethroo/config/hooks/PRE_TASK_EXECUTION.md

@@ -1 +1,15 @@
 # PRE_TASK_EXECUTION Hook
+
+## Test-Driven Development: RED → GREEN → REFACTOR
+
+Before writing production code for this task, follow this cycle for each increment:
+
+1. **RED** — Write one failing test and run it; confirm it fails for the
+   expected reason.
+2. **GREEN** — Write the minimal code to pass it (YAGNI); confirm it passes.
+3. **REFACTOR** — Clean up with the test green; re-run and confirm still green.
+
+Apply this only to the meaningful tests the test philosophy calls for (custom
+logic, critical paths, edge cases) — not to trivial, CRUD, or framework code.
+If a task warrants no new test under that philosophy, state why and implement
+directly.

package/templates/strikethroo/config/shared/anti-rationalization.md

@@ -0,0 +1,3 @@
+# Anti-rationalization
+
+A discipline survives pressure only if you refuse the excuse to skip it. When a thought in the "rationalization" column of the skill's table forms, treat it as a red flag and apply the binding rule instead. There is no "unless it matters" exception.

package/templates/strikethroo/config/shared/clarification-gate.md

@@ -0,0 +1,7 @@
+# Clarification Gate — Cadence & Approval
+
+When you have questions:
+
+- **One at a time.** Ask a single question, wait for the answer, then decide the next from it — do not dump a batch.
+- **Multiple-choice first.** When the question allows, offer options with a recommended default plus an open-ended "Other"; the user confirms in one word.
+- **Approval gate.** Present the resolved scope and get explicit confirmation before you write or update the plan.

package/templates/strikethroo/config/shared/verification-gate.md

@@ -0,0 +1,10 @@
+# Verification Gate — Evidence Before Claims
+
+Before stating that anything is complete, passing, or working:
+
+1. **IDENTIFY** the command or signal that proves the claim.
+2. **RUN** it fresh now — never rely on earlier output or a subagent's report.
+3. **READ** the full output and exit code.
+4. **VERIFY** it matches the claim, then state the result.
+
+Red-flag words — "should", "probably", "seems to", "looks like", a premature "Done!" — mean you have not run the gate. Run it.

package/dist-web/assets/channel-C1z4NHke.js

@@ -1 +0,0 @@
-import{U as a,C as n}from"./mermaid.core-C0ywvB_J.js";const t=(r,o)=>a.lang.round(n.parse(r)[o]);export{t as c};

package/dist-web/assets/classDiagram-4FO5ZUOK-D0BcCPc_.js

@@ -1 +0,0 @@
-import{s as a,a as s,c as e,C as t}from"./chunk-727SXJPM-CgGGmYGu.js";import{b as i}from"./mermaid.core-C0ywvB_J.js";import"./chunk-FMBD7UC4-Qn3q5Qhx.js";import"./chunk-ND2GUHAM-DDrXpr-b.js";import"./chunk-55IACEB6-DAnXzn2R.js";import"./chunk-2J33WTMH-BFdYIb-H.js";import"./index-DtUXMh0p.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dist-web/assets/classDiagram-v2-Q7XG4LA2-D0BcCPc_.js

@@ -1 +0,0 @@
-import{s as a,a as s,c as e,C as t}from"./chunk-727SXJPM-CgGGmYGu.js";import{b as i}from"./mermaid.core-C0ywvB_J.js";import"./chunk-FMBD7UC4-Qn3q5Qhx.js";import"./chunk-ND2GUHAM-DDrXpr-b.js";import"./chunk-55IACEB6-DAnXzn2R.js";import"./chunk-2J33WTMH-BFdYIb-H.js";import"./index-DtUXMh0p.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dist-web/assets/stateDiagram-v2-BHNVJYJU-CbmIerZp.js

@@ -1 +0,0 @@
-import{b as e,a as r,s as a,S as s}from"./chunk-AQP2D5EJ-B-eVBjow.js";import{b as i}from"./mermaid.core-C0ywvB_J.js";import"./chunk-55IACEB6-DAnXzn2R.js";import"./chunk-2J33WTMH-BFdYIb-H.js";import"./index-DtUXMh0p.js";var u={parser:a,get db(){return new s(2)},renderer:r,styles:e,init:i(t=>{t.state||(t.state={}),t.state.arrowMarkerAbsolute=t.arrowMarkerAbsolute},"init")};export{u as diagram};