npm - @jakkrichm/create-nexus-devflow - Versions diffs - 2.2.1 → 2.2.2 - Mend

@jakkrichm/create-nexus-devflow 2.2.1 → 2.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (21) hide show

package/dist/lib/gatekeeper.d.ts +4 -0
package/dist/lib/gatekeeper.js +13 -1
package/dist/lib/gatekeeper.js.map +1 -1
package/package.json +1 -1
package/template/.agents/skills/30-plan/SKILL.md +13 -7
package/template/.agents/skills/40-execute/SKILL.md +8 -11
package/template/.agents/skills/50-verify/SKILL.md +14 -7
package/template/.agents/skills/check/SKILL.md +19 -11
package/template/.agents/skills/debug/SKILL.md +4 -8
package/template/.agents/skills/feature/SKILL.md +8 -4
package/template/.agents/skills/implement/SKILL.md +12 -8
package/template/.claude/skills/30-plan/SKILL.md +13 -7
package/template/.claude/skills/40-execute/SKILL.md +8 -11
package/template/.claude/skills/50-verify/SKILL.md +14 -7
package/template/.claude/skills/check/SKILL.md +19 -11
package/template/.claude/skills/debug/SKILL.md +4 -8
package/template/.claude/skills/feature/SKILL.md +8 -4
package/template/.claude/skills/implement/SKILL.md +12 -8
package/template/devflow/build-plan.md +10 -0
package/template/devflow/context/ai-interaction.md +23 -7
package/template/devflow/context/coding-standards.md +17 -6

package/dist/lib/gatekeeper.d.ts CHANGED Viewed

@@ -12,6 +12,10 @@ export interface GateReport {
     warnings: string[];
     findingsBlockers: number;
     remainingTasks: number;
+    twoStage: {
+        stage1SpecFidelity: boolean;
+        stage2CodeQuality: boolean;
+    };
     summary: string;
 }
 export declare function evaluateGate(projectRoot: string, options?: GateOptions): Promise<GateReport>;

package/dist/lib/gatekeeper.js CHANGED Viewed

@@ -38,6 +38,8 @@ export async function evaluateGate(projectRoot, options = {}) {
         }
     }
     catch { }
+    const stage1SpecFidelity = remaining === 0 && (status.currentWork.state === "idle" || status.completion.state === "ready" || !options.strict);
+    const stage2CodeQuality = blockers.length === 0;
     const passed = violations.length === 0;
     const exitCode = passed ? 0 : 1;
     let summary = "";
@@ -45,7 +47,7 @@ export async function evaluateGate(projectRoot, options = {}) {
         summary =
             status.currentWork.state === "idle"
                 ? "Quality Gate Passed: Workspace is clean with 0 blockers."
-                : "Quality Gate Passed: Active run satisfies all gatekeeper criteria.";
+                : "Quality Gate Passed: Active run satisfies all gatekeeper criteria (Stage 1 Spec & Stage 2 Quality).";
     }
     else {
         summary = `Quality Gate Failed: ${violations.length} blocker(s) detected.`;
@@ -59,6 +61,10 @@ export async function evaluateGate(projectRoot, options = {}) {
         warnings,
         findingsBlockers: blockers.length,
         remainingTasks: remaining,
+        twoStage: {
+            stage1SpecFidelity,
+            stage2CodeQuality
+        },
         summary
     };
 }
@@ -72,6 +78,12 @@ export function formatGateReport(report, options = {}) {
     lines.push(header);
     lines.push(`  ${style.dim(report.summary)}`);
     lines.push("");
+    const s1Badge = report.twoStage.stage1SpecFidelity ? style.green("✔ PASS") : style.red("✖ FAIL");
+    const s2Badge = report.twoStage.stage2CodeQuality ? style.green("✔ PASS") : style.red("✖ FAIL");
+    lines.push(style.bold("Two-Stage Review Status:"));
+    lines.push(`  - Stage 1 (Spec Fidelity & Tasks) : ${s1Badge}`);
+    lines.push(`  - Stage 2 (Code Quality & Security): ${s2Badge}`);
+    lines.push("");
     if (report.violations.length > 0) {
         lines.push(style.bold(style.red("Violations:")));
         for (const v of report.violations) {

package/dist/lib/gatekeeper.js.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"gatekeeper.js","sourceRoot":"","sources":["../../lib/gatekeeper.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAEhD,OAAO,EAAE,cAAc,EAAE,MAAM,uBAAuB,CAAC;AACvD,OAAO,EAAE,WAAW,EAAE,MAAM,SAAS,CAAC;~~AAoBtC~~,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,WAAmB,EACnB,UAAuB,EAAE;IAEzB,MAAM,MAAM,GAAG,MAAM,iBAAiB,CAAC,WAAW,CAAC,CAAC;IACpD,MAAM,UAAU,GAAa,EAAE,CAAC;IAChC,MAAM,QAAQ,GAAa,EAAE,CAAC;IAE9B,sEAAsE;IACtE,MAAM,QAAQ,GAAG,MAAM,CAAC,QAAQ,CAAC,QAAQ,IAAI,EAAE,CAAC;IAChD,KAAK,MAAM,OAAO,IAAI,QAAQ,EAAE,CAAC;QAC/B,UAAU,CAAC,IAAI,CACb,WAAW,OAAO,CAAC,EAAE,KAAK,OAAO,CAAC,QAAQ,MAAM,OAAO,CAAC,MAAM,MAAM,OAAO,CAAC,KAAK,EAAE,CACpF,CAAC;IACJ,CAAC;IAED,oEAAoE;IACpE,MAAM,WAAW,GAAG,CAAC,MAAM,CAAC,QAAQ,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC,MAAM,CACvD,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,QAAQ,KAAK,IAAI,IAAI,IAAI,CAAC,QAAQ,KAAK,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,KAAK,MAAM,IAAI,IAAI,CAAC,MAAM,KAAK,YAAY,CAAC,CACzH,CAAC;IACF,KAAK,MAAM,IAAI,IAAI,WAAW,EAAE,CAAC;QAC/B,QAAQ,CAAC,IAAI,CACX,oBAAoB,IAAI,CAAC,EAAE,KAAK,IAAI,CAAC,QAAQ,MAAM,IAAI,CAAC,MAAM,MAAM,IAAI,CAAC,KAAK,EAAE,CACjF,CAAC;IACJ,CAAC;IAED,wCAAwC;IACxC,KAAK,MAAM,CAAC,IAAI,MAAM,CAAC,QAAQ,IAAI,EAAE,EAAE,CAAC;QACtC,QAAQ,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC,IAAI,MAAM,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC;IACrD,CAAC;IAED,4CAA4C;IAC5C,MAAM,SAAS,GAAG,MAAM,CAAC,WAAW,CAAC,SAAS,CAAC;IAC/C,IAAI,MAAM,CAAC,WAAW,CAAC,KAAK,KAAK,QAAQ,IAAI,SAAS,GAAG,CAAC,EAAE,CAAC;QAC3D,UAAU,CAAC,IAAI,CACb,gBAAgB,MAAM,CAAC,WAAW,CAAC,KAAK,IAAI,QAAQ,SAAS,SAAS,sBAAsB,CAC7F,CAAC;IACJ,CAAC;IAED,0CAA0C;IAC1C,IAAI,OAAO,CAAC,MAAM,IAAI,MAAM,CAAC,WAAW,CAAC,KAAK,KAAK,QAAQ,EAAE,CAAC;QAC5D,IAAI,MAAM,CAAC,UAAU,CAAC,KAAK,KAAK,oBAAoB,IAAI,MAAM,CAAC,UAAU,CAAC,KAAK,KAAK,SAAS,EAAE,CAAC;YAC9F,UAAU,CAAC,IAAI,CACb,gBAAgB,MAAM,CAAC,WAAW,CAAC,KAAK,IAAI,QAAQ,8CAA8C,CACnG,CAAC;QACJ,CAAC;IACH,CAAC;IAED,oCAAoC;IACpC,IAAI,CAAC;QACH,MAAM,KAAK,GAAG,MAAM,cAAc,CAAC,WAAW,CAAC,CAAC;QAChD,IAAI,KAAK,CAAC,QAAQ,IAAI,KAAK,CAAC,iBAAiB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACzD,QAAQ,CAAC,IAAI,CAAC,wBAAwB,KAAK,CAAC,iBAAiB,CAAC,MAAM,+DAA+D,CAAC,CAAC;QACvI,CAAC;IACH,CAAC;IAAC,MAAM,CAAC,CAAA,CAAC;~~IAGV~~,MAAM,MAAM,GAAG,UAAU,CAAC,MAAM,KAAK,CAAC,CAAC;IACvC,MAAM,QAAQ,GAAU,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;IAEvC,IAAI,OAAO,GAAG,EAAE,CAAC;IACjB,IAAI,MAAM,EAAE,CAAC;QACX,OAAO;YACL,MAAM,CAAC,WAAW,CAAC,KAAK,KAAK,MAAM;gBACjC,CAAC,CAAC,0DAA0D;gBAC5D,CAAC,CAAC,~~oEAAoE~~,CAAC;~~IAC7E~~,CAAC;SAAM,CAAC;QACN,OAAO,GAAG,wBAAwB,UAAU,CAAC,MAAM,uBAAuB,CAAC;IAC7E,CAAC;IAED,OAAO;QACL,MAAM;QACN,QAAQ;QACR,MAAM,EAAE,OAAO,CAAC,MAAM,KAAK,IAAI;QAC/B,eAAe,EAAE,MAAM,CAAC,UAAU,CAAC,KAAK;QACxC,UAAU;QACV,QAAQ;QACR,gBAAgB,EAAE,QAAQ,CAAC,MAAM;QACjC,cAAc,EAAE,SAAS;QACzB,OAAO;KACR,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,gBAAgB,CAC9B,MAAkB,EAClB,UAA+B,EAAE;IAEjC,MAAM,KAAK,GAAG,WAAW,CAAC,OAAO,CAAC,KAAK,CAAC,CAAC;IACzC,MAAM,KAAK,GAAa,EAAE,CAAC;IAE3B,MAAM,SAAS,GAAG,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,CAAC,MAAM,CAAC,eAAe,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,iBAAiB,CAAC,CAAC;IAC/F,MAAM,MAAM,GAAG,MAAM,CAAC,MAAM;QAC1B,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,iCAAiC,SAAS,EAAE,CAAC,CAAC;QACvE,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,kCAAkC,SAAS,EAAE,CAAC,CAAC,CAAC;IAEzE,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IACnB,KAAK,CAAC,IAAI,CAAC,KAAK,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC;IAC7C,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEf,IAAI,MAAM,CAAC,UAAU,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,aAAa,CAAC,CAAC,CAAC,CAAC;QACjD,KAAK,MAAM,CAAC,IAAI,MAAM,CAAC,UAAU,EAAE,CAAC;YAClC,KAAK,CAAC,IAAI,CAAC,OAAO,KAAK,CAAC,GAAG,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;QAC3C,CAAC;QACD,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACjB,CAAC;IAED,IAAI,MAAM,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC/B,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,wBAAwB,CAAC,CAAC,CAAC,CAAC;QAC/D,KAAK,MAAM,CAAC,IAAI,MAAM,CAAC,QAAQ,EAAE,CAAC;YAChC,KAAK,CAAC,IAAI,CAAC,OAAO,KAAK,CAAC,MAAM,CAAC,GAAG,CAAC,IAAI,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC;QACzD,CAAC;QACD,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACjB,CAAC;IAED,IAAI,MAAM,CAAC,UAAU,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,oBAAoB,CAAC,CAAC,CAAC;QAC/C,IAAI,MAAM,CAAC,gBAAgB,GAAG,CAAC,EAAE,CAAC;YAChC,KAAK,CAAC,IAAI,CAAC,yBAAyB,KAAK,CAAC,IAAI,CAAC,mCAAmC,CAAC,EAAE,CAAC,CAAC;QACzF,CAAC;QACD,IAAI,MAAM,CAAC,cAAc,GAAG,CAAC,EAAE,CAAC;YAC9B,KAAK,CAAC,IAAI,CAAC,uBAAuB,KAAK,CAAC,IAAI,CAAC,YAAY,CAAC,EAAE,CAAC,CAAC;QAChE,CAAC;QACD,IAAI,MAAM,CAAC,eAAe,KAAK,oBAAoB,IAAI,MAAM,CAAC,MAAM,EAAE,CAAC;YACrE,KAAK,CAAC,IAAI,CAAC,2BAA2B,KAAK,CAAC,IAAI,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC;QAChE,CAAC;IACH,CAAC;SAAM,CAAC;QACN,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,uDAAuD,CAAC,CAAC,CAAC;IACnF,CAAC;IAED,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,CAAC;AACpC,CAAC"}
1	+ {"version":3,"file":"gatekeeper.js","sourceRoot":"","sources":["../../lib/gatekeeper.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAEhD,OAAO,EAAE,cAAc,EAAE,MAAM,uBAAuB,CAAC;AACvD,OAAO,EAAE,WAAW,EAAE,MAAM,SAAS,CAAC;AAwBtC,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,WAAmB,EACnB,UAAuB,EAAE;IAEzB,MAAM,MAAM,GAAG,MAAM,iBAAiB,CAAC,WAAW,CAAC,CAAC;IACpD,MAAM,UAAU,GAAa,EAAE,CAAC;IAChC,MAAM,QAAQ,GAAa,EAAE,CAAC;IAE9B,sEAAsE;IACtE,MAAM,QAAQ,GAAG,MAAM,CAAC,QAAQ,CAAC,QAAQ,IAAI,EAAE,CAAC;IAChD,KAAK,MAAM,OAAO,IAAI,QAAQ,EAAE,CAAC;QAC/B,UAAU,CAAC,IAAI,CACb,WAAW,OAAO,CAAC,EAAE,KAAK,OAAO,CAAC,QAAQ,MAAM,OAAO,CAAC,MAAM,MAAM,OAAO,CAAC,KAAK,EAAE,CACpF,CAAC;IACJ,CAAC;IAED,oEAAoE;IACpE,MAAM,WAAW,GAAG,CAAC,MAAM,CAAC,QAAQ,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC,MAAM,CACvD,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,QAAQ,KAAK,IAAI,IAAI,IAAI,CAAC,QAAQ,KAAK,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,KAAK,MAAM,IAAI,IAAI,CAAC,MAAM,KAAK,YAAY,CAAC,CACzH,CAAC;IACF,KAAK,MAAM,IAAI,IAAI,WAAW,EAAE,CAAC;QAC/B,QAAQ,CAAC,IAAI,CACX,oBAAoB,IAAI,CAAC,EAAE,KAAK,IAAI,CAAC,QAAQ,MAAM,IAAI,CAAC,MAAM,MAAM,IAAI,CAAC,KAAK,EAAE,CACjF,CAAC;IACJ,CAAC;IAED,wCAAwC;IACxC,KAAK,MAAM,CAAC,IAAI,MAAM,CAAC,QAAQ,IAAI,EAAE,EAAE,CAAC;QACtC,QAAQ,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC,IAAI,MAAM,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC;IACrD,CAAC;IAED,4CAA4C;IAC5C,MAAM,SAAS,GAAG,MAAM,CAAC,WAAW,CAAC,SAAS,CAAC;IAC/C,IAAI,MAAM,CAAC,WAAW,CAAC,KAAK,KAAK,QAAQ,IAAI,SAAS,GAAG,CAAC,EAAE,CAAC;QAC3D,UAAU,CAAC,IAAI,CACb,gBAAgB,MAAM,CAAC,WAAW,CAAC,KAAK,IAAI,QAAQ,SAAS,SAAS,sBAAsB,CAC7F,CAAC;IACJ,CAAC;IAED,0CAA0C;IAC1C,IAAI,OAAO,CAAC,MAAM,IAAI,MAAM,CAAC,WAAW,CAAC,KAAK,KAAK,QAAQ,EAAE,CAAC;QAC5D,IAAI,MAAM,CAAC,UAAU,CAAC,KAAK,KAAK,oBAAoB,IAAI,MAAM,CAAC,UAAU,CAAC,KAAK,KAAK,SAAS,EAAE,CAAC;YAC9F,UAAU,CAAC,IAAI,CACb,gBAAgB,MAAM,CAAC,WAAW,CAAC,KAAK,IAAI,QAAQ,8CAA8C,CACnG,CAAC;QACJ,CAAC;IACH,CAAC;IAED,oCAAoC;IACpC,IAAI,CAAC;QACH,MAAM,KAAK,GAAG,MAAM,cAAc,CAAC,WAAW,CAAC,CAAC;QAChD,IAAI,KAAK,CAAC,QAAQ,IAAI,KAAK,CAAC,iBAAiB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACzD,QAAQ,CAAC,IAAI,CAAC,wBAAwB,KAAK,CAAC,iBAAiB,CAAC,MAAM,+DAA+D,CAAC,CAAC;QACvI,CAAC;IACH,CAAC;IAAC,MAAM,CAAC,CAAA,CAAC;IAEV,MAAM,kBAAkB,GAAG,SAAS,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,WAAW,CAAC,KAAK,KAAK,MAAM,IAAI,MAAM,CAAC,UAAU,CAAC,KAAK,KAAK,OAAO,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;IAC9I,MAAM,iBAAiB,GAAG,QAAQ,CAAC,MAAM,KAAK,CAAC,CAAC;IAEhD,MAAM,MAAM,GAAG,UAAU,CAAC,MAAM,KAAK,CAAC,CAAC;IACvC,MAAM,QAAQ,GAAU,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;IAEvC,IAAI,OAAO,GAAG,EAAE,CAAC;IACjB,IAAI,MAAM,EAAE,CAAC;QACX,OAAO;YACL,MAAM,CAAC,WAAW,CAAC,KAAK,KAAK,MAAM;gBACjC,CAAC,CAAC,0DAA0D;gBAC5D,CAAC,CAAC,qGAAqG,CAAC;IAC9G,CAAC;SAAM,CAAC;QACN,OAAO,GAAG,wBAAwB,UAAU,CAAC,MAAM,uBAAuB,CAAC;IAC7E,CAAC;IAED,OAAO;QACL,MAAM;QACN,QAAQ;QACR,MAAM,EAAE,OAAO,CAAC,MAAM,KAAK,IAAI;QAC/B,eAAe,EAAE,MAAM,CAAC,UAAU,CAAC,KAAK;QACxC,UAAU;QACV,QAAQ;QACR,gBAAgB,EAAE,QAAQ,CAAC,MAAM;QACjC,cAAc,EAAE,SAAS;QACzB,QAAQ,EAAE;YACR,kBAAkB;YAClB,iBAAiB;SAClB;QACD,OAAO;KACR,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,gBAAgB,CAC9B,MAAkB,EAClB,UAA+B,EAAE;IAEjC,MAAM,KAAK,GAAG,WAAW,CAAC,OAAO,CAAC,KAAK,CAAC,CAAC;IACzC,MAAM,KAAK,GAAa,EAAE,CAAC;IAE3B,MAAM,SAAS,GAAG,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,CAAC,MAAM,CAAC,eAAe,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,iBAAiB,CAAC,CAAC;IAC/F,MAAM,MAAM,GAAG,MAAM,CAAC,MAAM;QAC1B,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,iCAAiC,SAAS,EAAE,CAAC,CAAC;QACvE,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,kCAAkC,SAAS,EAAE,CAAC,CAAC,CAAC;IAEzE,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IACnB,KAAK,CAAC,IAAI,CAAC,KAAK,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC;IAC7C,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEf,MAAM,OAAO,GAAG,MAAM,CAAC,QAAQ,CAAC,kBAAkB,CAAC,CAAC,CAAC,KAAK,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;IACjG,MAAM,OAAO,GAAG,MAAM,CAAC,QAAQ,CAAC,iBAAiB,CAAC,CAAC,CAAC,KAAK,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;IAChG,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,0BAA0B,CAAC,CAAC,CAAC;IACnD,KAAK,CAAC,IAAI,CAAC,yCAAyC,OAAO,EAAE,CAAC,CAAC;IAC/D,KAAK,CAAC,IAAI,CAAC,0CAA0C,OAAO,EAAE,CAAC,CAAC;IAChE,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEf,IAAI,MAAM,CAAC,UAAU,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,aAAa,CAAC,CAAC,CAAC,CAAC;QACjD,KAAK,MAAM,CAAC,IAAI,MAAM,CAAC,UAAU,EAAE,CAAC;YAClC,KAAK,CAAC,IAAI,CAAC,OAAO,KAAK,CAAC,GAAG,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;QAC3C,CAAC;QACD,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACjB,CAAC;IAED,IAAI,MAAM,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC/B,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,wBAAwB,CAAC,CAAC,CAAC,CAAC;QAC/D,KAAK,MAAM,CAAC,IAAI,MAAM,CAAC,QAAQ,EAAE,CAAC;YAChC,KAAK,CAAC,IAAI,CAAC,OAAO,KAAK,CAAC,MAAM,CAAC,GAAG,CAAC,IAAI,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC;QACzD,CAAC;QACD,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACjB,CAAC;IAED,IAAI,MAAM,CAAC,UAAU,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,oBAAoB,CAAC,CAAC,CAAC;QAC/C,IAAI,MAAM,CAAC,gBAAgB,GAAG,CAAC,EAAE,CAAC;YAChC,KAAK,CAAC,IAAI,CAAC,yBAAyB,KAAK,CAAC,IAAI,CAAC,mCAAmC,CAAC,EAAE,CAAC,CAAC;QACzF,CAAC;QACD,IAAI,MAAM,CAAC,cAAc,GAAG,CAAC,EAAE,CAAC;YAC9B,KAAK,CAAC,IAAI,CAAC,uBAAuB,KAAK,CAAC,IAAI,CAAC,YAAY,CAAC,EAAE,CAAC,CAAC;QAChE,CAAC;QACD,IAAI,MAAM,CAAC,eAAe,KAAK,oBAAoB,IAAI,MAAM,CAAC,MAAM,EAAE,CAAC;YACrE,KAAK,CAAC,IAAI,CAAC,2BAA2B,KAAK,CAAC,IAAI,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC;QAChE,CAAC;IACH,CAAC;SAAM,CAAC;QACN,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,uDAAuD,CAAC,CAAC,CAAC;IACnF,CAAC;IAED,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,CAAC;AACpC,CAAC"}

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@jakkrichm/create-nexus-devflow",
-  "version": "2.2.1",
+  "version": "2.2.2",
   "description": "Installer package for Nexus-DevFlow agentic workflow layer.",
   "license": "MIT",
   "author": "Jakkrich",

package/template/.agents/skills/30-plan/SKILL.md CHANGED Viewed

@@ -83,12 +83,12 @@ Record important findings in `30-plan.md`. Use legacy context updates only when
 ### 4. Build The Plan
-Use the old planner discipline, but keep `30-plan.md` as the main contract:
+Use strict planning discipline, keeping `30-plan.md` as the main contract:
+- **Atomic Micro-Task Sizing (2–5 Minutes)**: Every subtask must be a small, verifiable unit that can be implemented and reviewed cleanly without context sprawl.
 - record the planning loop evidence: context read, observations, adjustments made, stop condition, and handoff notes
 - add phases in dependency order
-- add subtasks that are small, verifiable units
-- include explicit files to modify or create
+- include explicit files to modify or create (exact file paths)
 - include patterns to follow
 - include verification command or manual check
 - include a test decision for every subtask
@@ -97,18 +97,24 @@ Use the old planner discipline, but keep `30-plan.md` as the main contract:
 Each subtask should answer:
 - what to change
-- where to change it
+- where to change it (exact path)
 - which pattern to follow
 - how to verify it
 - whether automated tests are required, manual, or not required
-### 4.1 Test Decision Gate
+### 4.1 Strict TDD Task Breakdown & Test Decision Gate
-**STRICT MANDATE (กฎเหล็ก Unit Test)**: สำหรับทุก subtask ที่มีการเพิ่ม แก้ไข หรือเปลี่ยนแปลงการทำงานของโค้ด (Behavior Change) **ต้องระบุเป็น `Required` เสมอ** ห้ามละเว้นเด็ดขาด ยกเว้นงานประเภทเอกสารหรือแก้ไข Configuration เท่านั้น
+**STRICT MANDATE (กฎเหล็ก Unit Test & TDD)**: สำหรับทุก subtask ที่มีการเพิ่ม แก้ไข หรือเปลี่ยนแปลงการทำงานของโค้ด (Behavior Change) **ต้องระบุเป็น `Required` เสมอ** และต้องย่อยงานเป็น **TDD Triplet Sub-tasks** ดังนี้:
+```markdown
+- [ ] Task 1.1 [TDD-Red]: Write failing test for {feature/behavior} in {test_file} and verify failure
+- [ ] Task 1.2 [TDD-Green]: Implement minimal code in {src_file} to satisfy Task 1.1 test
+- [ ] Task 1.3 [TDD-Refactor]: Refactor logic, eliminate duplication, and verify zero regression
+```
 For every subtask, decide one of:
-- `Required`: automated tests must be created or updated (Mandatory for all behavior changes)
+- `Required`: automated tests must be created or updated (Mandatory for all behavior changes, formatted as TDD Triplet)
 - `Manual/Command Only`: verification is non-test but still explicit (Only for configuration/infrastructure tasks)
 - `Not Required`: no new automated test is needed because there is no meaningful behavior surface (Only for documentation/comments)

package/template/.agents/skills/40-execute/SKILL.md CHANGED Viewed

@@ -59,27 +59,24 @@ Confirm the current Git branch with `git branch --show-current` and use that bra
 Select one scoped unit of work at a time. Do not implement the whole plan as one blob.
-### 2. Execute One Scoped Unit
+### 2. Execute One Scoped Unit (Strict TDD Red-Green-Refactor)
-Use the original coder discipline, adapted to 2.0:
+Use the strict coder discipline:
-- **STRICT MANDATE (กฎเหล็ก Unit Test)**: ต้องสร้าง/แก้ไข Unit Test ควบคู่กับการแก้ไขโค้ดเสมอ โดยห้ามแก้ไขเฉพาะไฟล์โค้ดหลัก (Production Code) โดยไม่แก้ไขหรือสร้างไฟล์เทสต์ควบคู่กัน
+- **STRICT MANDATE (กฎเหล็ก Unit Test & TDD)**: สำหรับทุกงานที่มีการแก้ไข logic การทำงาน ต้องสร้างหรือแก้ไข Unit Test ควบคู่กับการแก้ไขโค้ดเสมอ โดยห้ามเขียนเฉพาะ Production Code โดยไม่มีเทสต์
+- **🔴 RED (Test First)**: ออกแบบและเขียน Test Case ในไฟล์เทสต์ก่อนเสมอ แล้วรันคำสั่งเทสต์เพื่อพิสูจน์ว่า **Test ล้มเหลว (FAIL)** ตามที่คาดหวัง
+- **🟢 GREEN (Minimal Implementation)**: เขียน Production Code เท่าที่จำเป็นเพื่อให้เทสต์ผ่าน แล้วรันคำสั่งเทสต์เพื่อพิสูจน์ว่า **Test ผ่าน 100% (PASS)**
+- **🔵 REFACTOR (Clean Code)**: ปรับปรุงโครงสร้างโค้ดให้อ่านง่าย กำจัดความซ้ำซ้อน (DRY) โดยที่เทสต์ยังคงเขียว 100%
+- **Code Deletion / Reversion Rule**: หากเผลอเขียน Production Code ก่อนมีเทสต์ ให้ Revert หรือลบโค้ดส่วนนั้น แล้วเริ่มวงจร RED ก่อนเสมอ
 - start each scoped unit by naming its intent, context, expected observation, adjustment route, and stop condition
 - read referenced pattern files before editing
 - read the test decision from `30-plan.md`
 - confirm assumptions, target files, and success criteria before editing
-- make the smallest useful code change
 - preserve project style
-- run the planned verification
+- run the planned verification and capture concrete terminal outputs
 - record observation, adjustment, stop condition status, and the result in `40-execute.md`
 - update checklist item status, timestamps, and evidence links as work progresses
-If tests are `Required`:
-1. **TDD Cycle (RED)**: ออกแบบและเขียนตัวเทสต์ให้พังก่อน (หรือเขียนโครงสร้างเทสต์ที่คาดหวังผลลัพธ์ที่ถูกต้อง) ตามแนวทางใน [coding-standards.md](file:///devflow/context/coding-standards.md)
-2. **GREEN**: เขียนโค้ดระบบจริงให้สอดคล้องเพื่อให้เทสต์ผ่าน
-3. **REFACTOR**: ปรับปรุงโครงสร้างโค้ดโดยยังคงรันเทสต์ผ่านอย่างต่อเนื่อง
 ### 3. Recovery
 Use the old recovery discipline when blocked:

package/template/.agents/skills/50-verify/SKILL.md CHANGED Viewed

@@ -18,15 +18,21 @@ Review implementation quality, run multi-lane validation, produce a verification
 Use `50-verify.md` as the primary verification artifact.
 Use `50-verify-impact.md` as an optional companion artifact when the run changes behavior, touches core logic, crosses integration boundaries, or needs explicit rollback and client impact analysis.
-## Process & Quality Gates
+## Process & Quality Gates (Two-Stage Review Pattern)
-### 1. Senior QA Review & Multi-Lane Verification
+### Stage 1: Spec Fidelity & Acceptance Criteria Gate
+Before evaluating technical code metrics, verify that the implementation faithfully delivers what was specified:
+1. **Acceptance Criteria Validation**: Cross-check each Acceptance Criterion (AC-1, AC-2, ...) in `20-spec.md` or `current-feature.md` and verify concrete evidence of completion.
+2. **Done-When Observable Verification**: Check that all observable conditions ("Done when...") are satisfied in the running application or test suite.
+3. **Scope Discipline**: Ensure zero scope creep (no unrequested features added) and no unfulfilled functional requirements.
+4. **Boundary & Negative Scenarios**: Verify unhappy paths, empty inputs, and error states defined in the specification.
-Execute verification across all essential quality dimensions:
+### Stage 2: Code Quality, Security & Architecture Gate
+Execute multi-lane technical verification across all essential quality dimensions:
 1. **Lane 1: Typecheck & Static Code Quality**:
    - Run typecheck and static analysis (`tsc --noEmit`, `npm run lint`).
-2. **Lane 2: Automated Test Suites (TDD Gate)**:
+2. **Lane 2: Automated Test Suites (Strict TDD Gate)**:
    - Run automated unit and integration tests (`npm test`).
    - Confirm 100% test pass rate with zero disabled or skipped tests.
 3. **Lane 3: Scrutinize QA & Edge Cases Review**:
@@ -44,12 +50,13 @@ Execute verification across all essential quality dimensions:
 ### 2. Decision & Route
-- **Pass**: Route to `60-report {ID}`.
-- **Fail**: Route back to `40-execute {ID}` with exact failure evidence and remediation steps.
+- **Pass**: Both Stage 1 and Stage 2 pass with 0 blockers -> Route to `60-report {ID}`.
+- **Fail**: Either Stage 1 or Stage 2 fails -> Route back to `40-execute {ID}` with exact failure evidence and remediation steps.
 ## Output
 Report:
-- QA verdict across all verification lanes
+- **Stage 1 Verdict**: Spec Fidelity & Acceptance Criteria status
+- **Stage 2 Verdict**: Technical Multi-lane quality & security matrix
 - Evidence commands and outputs
 - Next command: `60-report {ID}` (if pass) or `40-execute {ID}` (if fail)

package/template/.agents/skills/check/SKILL.md CHANGED Viewed

@@ -66,21 +66,29 @@ Drive the app to each checklist item and capture evidence as you go:
 - Watch for **console errors and failed network requests**; a clean-looking screen
   with errors in the console is not a pass.
-## Step 4 - report
+## Step 4 - report (Two-Stage Review Pattern)
-Give a short, honest verdict, one line per checklist item:
+Format the verification report into two explicit review stages:
-    [pass] Download PDF saves certificate-<slug>.pdf - file downloaded, opened to the cert
-    [pass] Both buttons show a loading state - screenshot: loading-state.png
-    [fail] PDF border missing - printBackground not set; screenshot: pdf-no-border.png
-    [skip] Vercel render - can't verify locally (feature 9)
+### Stage 1: Spec Fidelity & Acceptance Gate
+Give a line-by-line verdict for each Acceptance Criterion and "done when" item:
-Then state the bottom line: are all the feature's done-whens proven, or not yet.
+    [pass] AC-1: Download PDF saves certificate-<slug>.pdf - file downloaded, opened to cert
+    [pass] AC-2: Both buttons show a loading state - screenshot: loading-state.png
+    [fail] AC-3: PDF border missing - printBackground not set; screenshot: pdf-no-border.png
+    [skip] AC-4: Vercel deploy smoke test - can't verify locally (pending staging)
-- All proven -> say it's ready for `/complete`.
-- Anything failed -> hand back to `/implement` to fix; name what to fix. Don't fix
-  it here.
-- Anything unverifiable -> say so plainly and why; never report it as a pass.
+### Stage 2: Code Quality, Security & Architecture Gate
+Report the multi-lane technical verification results:
+- **Type & Syntax**: `tsc --noEmit` (0 errors)
+- **Automated Tests**: Unit & integration tests (100% pass)
+- **Security & Hygiene**: Zero secrets, sanitized inputs
+- **Findings Ledger**: 0 blockers (P0/P1) in `devflow/context/findings.md`
+### Final Verdict & Route
+- **All Passed**: State that the feature is verified and ready for `/complete`.
+- **Any Failure**: Hand back to `/implement` with exact failure evidence and reproduction steps. Never fix issues inside `/check`.
+- **Unverifiable**: Clearly state reasons and residual risk. Never fabricate a pass.
 ## Rules

package/template/.agents/skills/debug/SKILL.md CHANGED Viewed

@@ -117,14 +117,10 @@ Give a concise debug report:
 Choose the next action without writing files:
-- Active feature or fix caused the failure -> return the diagnosis to
-  `/implement`.
-- No active work item and the bug is confirmed -> recommend
-  `/fix "<concise bug and confirmed cause>"`.
-- Cause is only likely or blocked -> recommend the next diagnostic evidence, not
-  a speculative repair.
-- The issue is planned product work rather than a defect -> point to
-  `/feature`.
+- Active feature or fix caused the failure -> return the diagnosis to `/implement` with instructions to write a failing reproduction test ([TDD-Red]) first.
+- No active work item and the bug is confirmed -> recommend `/fix "<concise bug and confirmed cause>"` (which will write a failing test first before fixing).
+- Cause is only likely or blocked -> recommend the next diagnostic evidence, not a speculative repair.
+- The issue is planned product work rather than a defect -> point to `/feature`.
 ## Rules

package/template/.agents/skills/feature/SKILL.md CHANGED Viewed

@@ -113,10 +113,14 @@ build plan starts high-level.
 For the one (sub-)feature being built now, write a full spec to
 `devflow/context/current-feature.md` (create `devflow/context/` if needed), following
-`reference/feature-spec-template.md`. Fill every section: goal, in/out of scope,
-the build loop, small build steps as a checklist (`- [ ]`, each with an observable
-"done when" - `/implement` ticks them off and resumes from the first unchecked
-one), files/areas, data/contracts, testing, and notes for the AI.
+`reference/feature-spec-template.md`. Fill every section:
+- Goal, Problem Statement, and In/Out of scope
+- Acceptance Criteria (AC-1, AC-2, ...)
+- Small build steps as atomic 2-5 min checklist items (`- [ ]`, supporting `[TDD-Red]`, `[TDD-Green]`, `[TDD-Refactor]` triplets for functional logic)
+- Two-Stage Verification Strategy:
+  - **Stage 1**: Spec Fidelity & Acceptance Criteria Gate
+  - **Stage 2**: Technical Multi-lane quality, tests, security, and findings ledger
+- Files/areas to modify, data/contracts, and notes for the AI.
 **Visual or replication features need a reference image.** If the feature is
 "make it look like X" - recreating an existing design, matching a mockup, or

package/template/.agents/skills/implement/SKILL.md CHANGED Viewed

@@ -88,19 +88,23 @@ broad checkout. Ask whether to resolve only the conflict allowed by the approved
 spec or abandon the attempt. A cascade into another completed feature needs a
 new rollback plan.
-## Step 2 - build one step, review, iterate, checkpoint
+## Step 2 - build one step, review, iterate, checkpoint (Strict TDD)
 Work through the spec's build steps in order, one at a time. For each step:
-1. Implement just that step: the smallest change that satisfies its "done when."
-2. Show the **diff**, not whole files.
-3. **Explain it, and prove it.** Give a short summary: what the step delivered,
+1. **Strict TDD Cycle (for logic & behavior changes)**:
+   - **🔴 RED**: Write the unit test first in the relevant test file. Execute the test command and show the failing assertion output.
+   - **🟢 GREEN**: Implement only the minimal code in the source file necessary to make the test pass. Re-run test and show passing output.
+   - **🔵 REFACTOR**: Refactor and format cleanly, verifying that 100% of tests remain green.
+   - *Code Reversion Rule*: If production code is written without a prior test for behavior changes, revert it and write the test first.
+2. Implement just that step: the smallest change that satisfies its "done when."
+3. Show the **diff**, not whole files.
+4. **Explain it, and prove it.** Give a short summary: what the step delivered,
    one line per changed file on what it does and why, then confirm the step's
-   "done when" is met with evidence (build output, a screenshot, a passing
-   assertion). This summary is the comprehension gate, so keep it concrete, not
-   ceremonial. Include a short **How to try it** note when the step has a manual
+   "done when" is met with empirical evidence (test pass output, build output, or screenshot). This summary is the comprehension gate, so keep it concrete, not
+   vague. Include a short **How to try it** note when the step has a manual
    path: the command, URL, click, endpoint, or output the user can check.
-4. **Verify the step.** If `AGENTS.md` declares a `Verify` command, run that exact
+5. **Verify the step.** If `AGENTS.md` declares a `Verify` command, run that exact
    command as the automated gate. It is only an umbrella for checks the project
    actually has, so do not invent tests or other checks to satisfy it. If no
    `Verify` command exists, run the documented build command and the test command

package/template/.claude/skills/30-plan/SKILL.md CHANGED Viewed

@@ -83,12 +83,12 @@ Record important findings in `30-plan.md`. Use legacy context updates only when
 ### 4. Build The Plan
-Use the old planner discipline, but keep `30-plan.md` as the main contract:
+Use strict planning discipline, keeping `30-plan.md` as the main contract:
+- **Atomic Micro-Task Sizing (2–5 Minutes)**: Every subtask must be a small, verifiable unit that can be implemented and reviewed cleanly without context sprawl.
 - record the planning loop evidence: context read, observations, adjustments made, stop condition, and handoff notes
 - add phases in dependency order
-- add subtasks that are small, verifiable units
-- include explicit files to modify or create
+- include explicit files to modify or create (exact file paths)
 - include patterns to follow
 - include verification command or manual check
 - include a test decision for every subtask
@@ -97,18 +97,24 @@ Use the old planner discipline, but keep `30-plan.md` as the main contract:
 Each subtask should answer:
 - what to change
-- where to change it
+- where to change it (exact path)
 - which pattern to follow
 - how to verify it
 - whether automated tests are required, manual, or not required
-### 4.1 Test Decision Gate
+### 4.1 Strict TDD Task Breakdown & Test Decision Gate
-**STRICT MANDATE (กฎเหล็ก Unit Test)**: สำหรับทุก subtask ที่มีการเพิ่ม แก้ไข หรือเปลี่ยนแปลงการทำงานของโค้ด (Behavior Change) **ต้องระบุเป็น `Required` เสมอ** ห้ามละเว้นเด็ดขาด ยกเว้นงานประเภทเอกสารหรือแก้ไข Configuration เท่านั้น
+**STRICT MANDATE (กฎเหล็ก Unit Test & TDD)**: สำหรับทุก subtask ที่มีการเพิ่ม แก้ไข หรือเปลี่ยนแปลงการทำงานของโค้ด (Behavior Change) **ต้องระบุเป็น `Required` เสมอ** และต้องย่อยงานเป็น **TDD Triplet Sub-tasks** ดังนี้:
+```markdown
+- [ ] Task 1.1 [TDD-Red]: Write failing test for {feature/behavior} in {test_file} and verify failure
+- [ ] Task 1.2 [TDD-Green]: Implement minimal code in {src_file} to satisfy Task 1.1 test
+- [ ] Task 1.3 [TDD-Refactor]: Refactor logic, eliminate duplication, and verify zero regression
+```
 For every subtask, decide one of:
-- `Required`: automated tests must be created or updated (Mandatory for all behavior changes)
+- `Required`: automated tests must be created or updated (Mandatory for all behavior changes, formatted as TDD Triplet)
 - `Manual/Command Only`: verification is non-test but still explicit (Only for configuration/infrastructure tasks)
 - `Not Required`: no new automated test is needed because there is no meaningful behavior surface (Only for documentation/comments)

package/template/.claude/skills/40-execute/SKILL.md CHANGED Viewed

@@ -59,27 +59,24 @@ Confirm the current Git branch with `git branch --show-current` and use that bra
 Select one scoped unit of work at a time. Do not implement the whole plan as one blob.
-### 2. Execute One Scoped Unit
+### 2. Execute One Scoped Unit (Strict TDD Red-Green-Refactor)
-Use the original coder discipline, adapted to 2.0:
+Use the strict coder discipline:
-- **STRICT MANDATE (กฎเหล็ก Unit Test)**: ต้องสร้าง/แก้ไข Unit Test ควบคู่กับการแก้ไขโค้ดเสมอ โดยห้ามแก้ไขเฉพาะไฟล์โค้ดหลัก (Production Code) โดยไม่แก้ไขหรือสร้างไฟล์เทสต์ควบคู่กัน
+- **STRICT MANDATE (กฎเหล็ก Unit Test & TDD)**: สำหรับทุกงานที่มีการแก้ไข logic การทำงาน ต้องสร้างหรือแก้ไข Unit Test ควบคู่กับการแก้ไขโค้ดเสมอ โดยห้ามเขียนเฉพาะ Production Code โดยไม่มีเทสต์
+- **🔴 RED (Test First)**: ออกแบบและเขียน Test Case ในไฟล์เทสต์ก่อนเสมอ แล้วรันคำสั่งเทสต์เพื่อพิสูจน์ว่า **Test ล้มเหลว (FAIL)** ตามที่คาดหวัง
+- **🟢 GREEN (Minimal Implementation)**: เขียน Production Code เท่าที่จำเป็นเพื่อให้เทสต์ผ่าน แล้วรันคำสั่งเทสต์เพื่อพิสูจน์ว่า **Test ผ่าน 100% (PASS)**
+- **🔵 REFACTOR (Clean Code)**: ปรับปรุงโครงสร้างโค้ดให้อ่านง่าย กำจัดความซ้ำซ้อน (DRY) โดยที่เทสต์ยังคงเขียว 100%
+- **Code Deletion / Reversion Rule**: หากเผลอเขียน Production Code ก่อนมีเทสต์ ให้ Revert หรือลบโค้ดส่วนนั้น แล้วเริ่มวงจร RED ก่อนเสมอ
 - start each scoped unit by naming its intent, context, expected observation, adjustment route, and stop condition
 - read referenced pattern files before editing
 - read the test decision from `30-plan.md`
 - confirm assumptions, target files, and success criteria before editing
-- make the smallest useful code change
 - preserve project style
-- run the planned verification
+- run the planned verification and capture concrete terminal outputs
 - record observation, adjustment, stop condition status, and the result in `40-execute.md`
 - update checklist item status, timestamps, and evidence links as work progresses
-If tests are `Required`:
-1. **TDD Cycle (RED)**: ออกแบบและเขียนตัวเทสต์ให้พังก่อน (หรือเขียนโครงสร้างเทสต์ที่คาดหวังผลลัพธ์ที่ถูกต้อง) ตามแนวทางใน [coding-standards.md](file:///devflow/context/coding-standards.md)
-2. **GREEN**: เขียนโค้ดระบบจริงให้สอดคล้องเพื่อให้เทสต์ผ่าน
-3. **REFACTOR**: ปรับปรุงโครงสร้างโค้ดโดยยังคงรันเทสต์ผ่านอย่างต่อเนื่อง
 ### 3. Recovery
 Use the old recovery discipline when blocked:

package/template/.claude/skills/50-verify/SKILL.md CHANGED Viewed

@@ -18,15 +18,21 @@ Review implementation quality, run multi-lane validation, produce a verification
 Use `50-verify.md` as the primary verification artifact.
 Use `50-verify-impact.md` as an optional companion artifact when the run changes behavior, touches core logic, crosses integration boundaries, or needs explicit rollback and client impact analysis.
-## Process & Quality Gates
+## Process & Quality Gates (Two-Stage Review Pattern)
-### 1. Senior QA Review & Multi-Lane Verification
+### Stage 1: Spec Fidelity & Acceptance Criteria Gate
+Before evaluating technical code metrics, verify that the implementation faithfully delivers what was specified:
+1. **Acceptance Criteria Validation**: Cross-check each Acceptance Criterion (AC-1, AC-2, ...) in `20-spec.md` or `current-feature.md` and verify concrete evidence of completion.
+2. **Done-When Observable Verification**: Check that all observable conditions ("Done when...") are satisfied in the running application or test suite.
+3. **Scope Discipline**: Ensure zero scope creep (no unrequested features added) and no unfulfilled functional requirements.
+4. **Boundary & Negative Scenarios**: Verify unhappy paths, empty inputs, and error states defined in the specification.
-Execute verification across all essential quality dimensions:
+### Stage 2: Code Quality, Security & Architecture Gate
+Execute multi-lane technical verification across all essential quality dimensions:
 1. **Lane 1: Typecheck & Static Code Quality**:
    - Run typecheck and static analysis (`tsc --noEmit`, `npm run lint`).
-2. **Lane 2: Automated Test Suites (TDD Gate)**:
+2. **Lane 2: Automated Test Suites (Strict TDD Gate)**:
    - Run automated unit and integration tests (`npm test`).
    - Confirm 100% test pass rate with zero disabled or skipped tests.
 3. **Lane 3: Scrutinize QA & Edge Cases Review**:
@@ -44,12 +50,13 @@ Execute verification across all essential quality dimensions:
 ### 2. Decision & Route
-- **Pass**: Route to `60-report {ID}`.
-- **Fail**: Route back to `40-execute {ID}` with exact failure evidence and remediation steps.
+- **Pass**: Both Stage 1 and Stage 2 pass with 0 blockers -> Route to `60-report {ID}`.
+- **Fail**: Either Stage 1 or Stage 2 fails -> Route back to `40-execute {ID}` with exact failure evidence and remediation steps.
 ## Output
 Report:
-- QA verdict across all verification lanes
+- **Stage 1 Verdict**: Spec Fidelity & Acceptance Criteria status
+- **Stage 2 Verdict**: Technical Multi-lane quality & security matrix
 - Evidence commands and outputs
 - Next command: `60-report {ID}` (if pass) or `40-execute {ID}` (if fail)

package/template/.claude/skills/check/SKILL.md CHANGED Viewed

@@ -66,21 +66,29 @@ Drive the app to each checklist item and capture evidence as you go:
 - Watch for **console errors and failed network requests**; a clean-looking screen
   with errors in the console is not a pass.
-## Step 4 - report
+## Step 4 - report (Two-Stage Review Pattern)
-Give a short, honest verdict, one line per checklist item:
+Format the verification report into two explicit review stages:
-    [pass] Download PDF saves certificate-<slug>.pdf - file downloaded, opened to the cert
-    [pass] Both buttons show a loading state - screenshot: loading-state.png
-    [fail] PDF border missing - printBackground not set; screenshot: pdf-no-border.png
-    [skip] Vercel render - can't verify locally (feature 9)
+### Stage 1: Spec Fidelity & Acceptance Gate
+Give a line-by-line verdict for each Acceptance Criterion and "done when" item:
-Then state the bottom line: are all the feature's done-whens proven, or not yet.
+    [pass] AC-1: Download PDF saves certificate-<slug>.pdf - file downloaded, opened to cert
+    [pass] AC-2: Both buttons show a loading state - screenshot: loading-state.png
+    [fail] AC-3: PDF border missing - printBackground not set; screenshot: pdf-no-border.png
+    [skip] AC-4: Vercel deploy smoke test - can't verify locally (pending staging)
-- All proven -> say it's ready for `/complete`.
-- Anything failed -> hand back to `/implement` to fix; name what to fix. Don't fix
-  it here.
-- Anything unverifiable -> say so plainly and why; never report it as a pass.
+### Stage 2: Code Quality, Security & Architecture Gate
+Report the multi-lane technical verification results:
+- **Type & Syntax**: `tsc --noEmit` (0 errors)
+- **Automated Tests**: Unit & integration tests (100% pass)
+- **Security & Hygiene**: Zero secrets, sanitized inputs
+- **Findings Ledger**: 0 blockers (P0/P1) in `devflow/context/findings.md`
+### Final Verdict & Route
+- **All Passed**: State that the feature is verified and ready for `/complete`.
+- **Any Failure**: Hand back to `/implement` with exact failure evidence and reproduction steps. Never fix issues inside `/check`.
+- **Unverifiable**: Clearly state reasons and residual risk. Never fabricate a pass.
 ## Rules

package/template/.claude/skills/debug/SKILL.md CHANGED Viewed

@@ -117,14 +117,10 @@ Give a concise debug report:
 Choose the next action without writing files:
-- Active feature or fix caused the failure -> return the diagnosis to
-  `/implement`.
-- No active work item and the bug is confirmed -> recommend
-  `/fix "<concise bug and confirmed cause>"`.
-- Cause is only likely or blocked -> recommend the next diagnostic evidence, not
-  a speculative repair.
-- The issue is planned product work rather than a defect -> point to
-  `/feature`.
+- Active feature or fix caused the failure -> return the diagnosis to `/implement` with instructions to write a failing reproduction test ([TDD-Red]) first.
+- No active work item and the bug is confirmed -> recommend `/fix "<concise bug and confirmed cause>"` (which will write a failing test first before fixing).
+- Cause is only likely or blocked -> recommend the next diagnostic evidence, not a speculative repair.
+- The issue is planned product work rather than a defect -> point to `/feature`.
 ## Rules

package/template/.claude/skills/feature/SKILL.md CHANGED Viewed

@@ -113,10 +113,14 @@ build plan starts high-level.
 For the one (sub-)feature being built now, write a full spec to
 `devflow/context/current-feature.md` (create `devflow/context/` if needed), following
-`reference/feature-spec-template.md`. Fill every section: goal, in/out of scope,
-the build loop, small build steps as a checklist (`- [ ]`, each with an observable
-"done when" - `/implement` ticks them off and resumes from the first unchecked
-one), files/areas, data/contracts, testing, and notes for the AI.
+`reference/feature-spec-template.md`. Fill every section:
+- Goal, Problem Statement, and In/Out of scope
+- Acceptance Criteria (AC-1, AC-2, ...)
+- Small build steps as atomic 2-5 min checklist items (`- [ ]`, supporting `[TDD-Red]`, `[TDD-Green]`, `[TDD-Refactor]` triplets for functional logic)
+- Two-Stage Verification Strategy:
+  - **Stage 1**: Spec Fidelity & Acceptance Criteria Gate
+  - **Stage 2**: Technical Multi-lane quality, tests, security, and findings ledger
+- Files/areas to modify, data/contracts, and notes for the AI.
 **Visual or replication features need a reference image.** If the feature is
 "make it look like X" - recreating an existing design, matching a mockup, or

package/template/.claude/skills/implement/SKILL.md CHANGED Viewed

@@ -88,19 +88,23 @@ broad checkout. Ask whether to resolve only the conflict allowed by the approved
 spec or abandon the attempt. A cascade into another completed feature needs a
 new rollback plan.
-## Step 2 - build one step, review, iterate, checkpoint
+## Step 2 - build one step, review, iterate, checkpoint (Strict TDD)
 Work through the spec's build steps in order, one at a time. For each step:
-1. Implement just that step: the smallest change that satisfies its "done when."
-2. Show the **diff**, not whole files.
-3. **Explain it, and prove it.** Give a short summary: what the step delivered,
+1. **Strict TDD Cycle (for logic & behavior changes)**:
+   - **🔴 RED**: Write the unit test first in the relevant test file. Execute the test command and show the failing assertion output.
+   - **🟢 GREEN**: Implement only the minimal code in the source file necessary to make the test pass. Re-run test and show passing output.
+   - **🔵 REFACTOR**: Refactor and format cleanly, verifying that 100% of tests remain green.
+   - *Code Reversion Rule*: If production code is written without a prior test for behavior changes, revert it and write the test first.
+2. Implement just that step: the smallest change that satisfies its "done when."
+3. Show the **diff**, not whole files.
+4. **Explain it, and prove it.** Give a short summary: what the step delivered,
    one line per changed file on what it does and why, then confirm the step's
-   "done when" is met with evidence (build output, a screenshot, a passing
-   assertion). This summary is the comprehension gate, so keep it concrete, not
-   ceremonial. Include a short **How to try it** note when the step has a manual
+   "done when" is met with empirical evidence (test pass output, build output, or screenshot). This summary is the comprehension gate, so keep it concrete, not
+   vague. Include a short **How to try it** note when the step has a manual
    path: the command, URL, click, endpoint, or output the user can check.
-4. **Verify the step.** If `AGENTS.md` declares a `Verify` command, run that exact
+5. **Verify the step.** If `AGENTS.md` declares a `Verify` command, run that exact
    command as the automated gate. It is only an umbrella for checks the project
    actually has, so do not invent tests or other checks to satisfy it. If no
    `Verify` command exists, run the documented build command and the test command

package/template/devflow/build-plan.md CHANGED Viewed

@@ -68,3 +68,13 @@
   - *Dependencies*: None
   - *Scope*: ผสานความสามารถ Adopt Workflow Visibility (Commit vs Local-only), การรองรับ OpenCode และ Multi-Adapter Checkbox Prompt ใน CLI พร้อมอัปเดต Doctor checks และซิงก์ Baseline SHA เป็น v0.13.0 (`0b65166`)
+---
+## 🧪 Phase 9: Strict TDD Sub-Tasks & Two-Stage Review Guardrails
+- [x] **9. Strict TDD Sub-Tasks & Two-Stage Review Guardrails** `[Size: M]`
+  - *Dependencies*: None
+  - *Scope*: นำ Strict TDD (Red-Green-Refactor) Sub-Tasks และ Two-Stage Review Pattern (Stage 1: Spec Fidelity, Stage 2: Quality & Security Gate) ผสานเข้าสู่ Prompt Rules, Coding Standards, AI Interaction และ Stage Skills (`30-plan`, `40-execute`, `50-verify`, `feature`, `implement`, `check`, `debug`) พร้อมอัปเดต Template และ Unit Tests

package/template/devflow/context/ai-interaction.md CHANGED Viewed

@@ -65,21 +65,37 @@ The entire lifecycle is driven by the **Single Living Spec (`devflow/context/cur
 *Recommended for large architectural epics, database migrations, security audits, and multi-agent coordination.*
 ```text
-00-explore ➔ 10-define ➔ 20-spec ➔ 30-plan ➔ 40-execute ➔ 50-verify ➔ 60-report ➔ 70-deliver
+discovery ➔ 10-define ➔ 20-spec ➔ 30-plan ➔ 40-execute ➔ 50-verify ➔ 60-report ➔ 70-deliver
 ```
-1. `00-explore`: Explore request before delivery commitment (`DISC-YYYYMMDD-NNN`).
+1. `discovery`: Unified pre-delivery discovery & Socratic alignment (`DISC-YYYYMMDD-NNN` or project roadmap).
 2. `10-define`: Turn approved discovery into bounded delivery run in `devflow/context/current-run/10-define.md`.
 3. `20-spec`: Formalize markdown delivery contract & acceptance criteria (`20-spec.md`).
-4. `30-plan`: Breakdown spec into executable tasks with test decisions (`30-plan.md` + checklists).
-5. `40-execute`: Incremental task execution behind review gates (`40-execute.md`).
-6. `50-verify`: Senior QA review & multi-lane verification checks (`50-verify.md`).
+4. `30-plan`: Breakdown spec into atomic 2-5 min tasks with explicit TDD decisions (`30-plan.md` + checklists).
+5. `40-execute`: Strict Red-Green-Refactor task execution behind review gates (`40-execute.md`).
+6. `50-verify`: Senior QA Two-Stage Review (Spec Fidelity + Quality/Security Gate) (`50-verify.md`).
 7. `60-report`: Standardized markdown delivery digest (`60-report.md`).
-8. `70-deliver`: Release packaging, git merge, archives `devflow/context/current-run/` ➔ `devflow/history/{features|fixes|rollbacks}/{xxx-slug}/`, and closes the run.
+8. `70-deliver`: Release packaging, git merge, archives `devflow/context/current-run/` ➔ `devflow/history/{category}/{xxx-slug}/`, and closes the run.
 ---
-## 4. Standalone HTML Reporting Policy
+## 4. Strict TDD & Two-Stage Review Interaction Rules
+### 🔴🟢 Strict TDD Execution Discipline
+During implementation in `/implement` and `40-execute`:
+- **Show Red Phase**: First execute tests to demonstrate expected failure *before* adding production code.
+- **Show Green Phase**: Add minimal production code, re-run tests, and report pass rate.
+- **Show Refactor Phase**: Polish and clean up with zero test regression.
+- **Forbidden**: Never present functional code changes without matching test execution evidence.
+### 🛡️ Two-Stage Verification Reporting
+During `/check` and `50-verify`:
+- **Stage 1 (Spec Fidelity Gate)**: Report each Acceptance Criterion and "Done When" status.
+- **Stage 2 (Code Quality & Security Gate)**: Report Typecheck, Lint, Test Suites, Security checks, and Findings Ledger (0 blockers).
+---
+## 5. Standalone HTML Reporting Policy
 > [!IMPORTANT]
 > **No Auto-Generated HTML**: Mainline stages (`/complete` and `60-report`) strictly output Markdown only.

package/template/devflow/context/coding-standards.md CHANGED Viewed

@@ -91,22 +91,33 @@ nexus-devflow/
 ---
-## 7. Testing & Empirical Proof Standards
+## 7. Testing & Empirical Proof Standards (Strict TDD & Two-Stage Review)
 Testing is a core quality gate in Nexus-DevFlow, not an afterthought:
 - **Unit Test Mandate**: Any new feature, modified logic, parser improvement, or bug fix **MUST ship with automated unit tests** in the same diff.
+- **Strict TDD (Red-Green-Refactor) Protocol**:
+  1. **🔴 RED (Test First)**: Always write automated tests *before* writing or modifying functional logic. Run the test command and verify that it fails for the expected reason.
+  2. **🟢 GREEN (Minimal Code)**: Write only the minimal production code necessary to make the failing test pass. Run the test command and verify 100% green pass.
+  3. **🔵 REFACTOR (Clean & Robust)**: Refactor code for readability, performance, and DRY/YAGNI discipline while ensuring all tests stay green.
+  - *Code Deletion / Reversion Rule*: If functional code is created without a prior failing test for behavior changes, it must be reverted or immediately backed by tests before continuing.
 - **Test Framework**: Use Node.js native test runner executed via `tsx --test test/*.test.ts` under `packages/create-nexus-devflow/`.
 - **Test Design (AAA Pattern)**:
   - Structure each test case cleanly: **Arrange** (setup fixtures/mock directories), **Act** (execute function), **Assert** (verify invariants).
   - Use isolated temporary directories (`fs.mkdtemp` in `os.tmpdir()`) and ensure cleanup in `finally` blocks.
 - **Empirical Proof Contract**:
   - Never claim a task is "working", "tested", or "verified" without providing concrete empirical proof (exact command executed, terminal output, pass/fail counts, exit code).
-- **Multi-Lane Verification Matrix**:
-  - **Lane 1 (Type & Syntax Safety)**: `tsc --noEmit` (0 type errors).
-  - **Lane 2 (Automated Test Suites & Evals)**: `npm test` (Unit tests 100% pass) + `npm run test:routing` (Skill routing accuracy).
-  - **Lane 3 (Scrutinize & Security Audit)**: Edge cases, null-safety, 0 secrets, safe inputs.
-  - **Lane 4 (Manual / Scenario Proof)**: Concrete walkthrough steps ("Where to go", "What to run", "What to expect").
+- **Two-Stage Review Pattern (Verification Gate)**:
+  - **Stage 1: Spec Fidelity & Acceptance Gate**:
+    - Verify 100% conformance against the living spec (`current-feature.md` or `20-spec.md`).
+    - Validate all Acceptance Criteria (ACs) and "Done When" observables without missing requirements or scope creep.
+    - Test edge cases and boundary conditions defined in the specification.
+  - **Stage 2: Code Quality, Security & Architecture Gate**:
+    - **Lane 1 (Type & Syntax Safety)**: `tsc --noEmit` (0 type errors).
+    - **Lane 2 (Automated Test Suites & Evals)**: `npm test` (Unit tests 100% pass) + `npm run test:routing` (Skill routing accuracy).
+    - **Lane 3 (Scrutinize & Security Audit)**: Edge cases, null-safety, 0 secrets, safe inputs.
+    - **Lane 4 (Manual / Scenario Proof)**: Concrete walkthrough steps ("Where to go", "What to run", "What to expect").
+    - **Findings Ledger State**: 0 blockers (P0/P1) in `devflow/context/findings.md`.
 ---