@haposoft/cafekit 0.7.18 → 0.7.20

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haposoft/cafekit",
-  "version": "0.7.18",
+  "version": "0.7.20",
   "description": "Spec-Driven Development workflow for AI coding assistants. Supports Claude Code and Antigravity with spec-first workflows plus Claude Code hapo: skills.",
   "author": "Haposoft <nghialt@haposoft.com>",
   "license": "MIT",

package/src/claude/skills/specs/SKILL.md

@@ -2,7 +2,7 @@
 name: hapo:specs
 description: "Structured specification workflow — from vague idea to actionable task list. Includes init, requirements, design, task breakdown, review, and archiving."
 version: 2.0.0
-argument-hint: "<feature-description> | status | resume | review | archive"
+argument-hint: "<feature-description> | status | resume | --validate | archive"
 ---
 
 # Specs (SDD — Specification-Driven Development)
@@ -67,7 +67,7 @@ Display selection menu via `AskUserQuestion`:
       { "label": "Create new spec", "description": "Initialize spec from a feature description" },
       { "label": "status", "description": "View status of all specs in specs/" },
       { "label": "resume", "description": "Continue an in-progress spec" },
-      { "label": "review", "description": "Review spec (auto-decides: red team or validation)" },
+      { "label": "--validate", "description": "Review spec (auto-decides: red team or validation)" },
       { "label": "archive", "description": "Archive completed specs + write journal" }
     ],
     "multiSelect": false
@@ -82,12 +82,17 @@ System auto-analyzes the description:
 - If task is simple (small bugfix, config change) → suggest "A spec may not be needed for this. Continue anyway?"
 - If task is complex (multi-module, security/migration related) → auto-activate deep research, ask user 3 scope questions
 
+### When called WITH `--validate` argument
+
+System IMMEDIATELY jumps to **Step 9: Validation Review**.
+The system MUST NOT execute Steps 1-8. Instead, load `references/review.md`, adopt Red Team personas, and read the entire `specs/` directory to hunt for flaws before interviewing the user.
+
 ## Workflow Diagram
 
 ```mermaid
 flowchart TD
     A["Call /hapo:specs"] --> B{Has description?}
-    B -->|No| C["Menu: init / status / resume / review / archive"]
+    B -->|No| C["Menu: init / status / resume / --validate / archive"]
     B -->|Yes| D["Step 1: Analyze description"]
     D --> E{Clear enough?}
     E -->|No| F["Ask user 1-2 clarifying questions"]
@@ -257,7 +262,7 @@ Load: `references/task-hydration.md`
 - If TaskCreate tool unavailable → fallback to `TodoWrite`
 - Task files are the single source of truth — hydration is just a convenience
 
-### Step 9: Review (Optional)
+### Step 9: Validation Review (Optional)
 Load: `references/review.md` + `rules/design-review.md`
 - System auto-evaluates spec complexity and decides review depth:
   - **< 3 task files, no security concerns** → Validate only (lightweight interview)
@@ -342,7 +347,7 @@ specs/
 |---|---|---|
 | `/hapo:specs status` | View status of all specs | — |
 | `/hapo:specs resume <feature>` | Continue an in-progress spec | — |
-| `/hapo:specs review <feature>` | Review spec (auto: red team + validate based on complexity) | `references/review.md` |
+| `/hapo:specs --validate <feature>` | Validate spec (auto: red team + validate based on complexity) | `references/review.md` |
 | `/hapo:specs archive` | Archive completed specs + write journal | `references/archive-workflow.md` |
 
 ## Quality Standards