@haposoft/cafekit 0.7.13 → 0.7.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haposoft/cafekit",
-  "version": "0.7.13",
+  "version": "0.7.15",
   "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/rules/tasks-generation.md

@@ -11,15 +11,17 @@ Focus on capabilities and outcomes, not code structure.
 - Features and capabilities
 - Domain language and concepts
 - Data relationships and workflows
-
-**Avoid**:
-- File paths and directory structure
-- Function/method names and signatures
-- Type definitions and interfaces
-- Class names and API contracts
-- Specific data structures
-
-**Rationale**: Implementation details (files, methods, types) are defined in design.md. Tasks describe the functional work to be done.
+**Required (Hybrid Human-AI Style)**:
+Every sub-task MUST balance Human Intent (for PM review) and Code-Level Details (for AI implementation).
+Detail bullets must include:
+1. **Human Intent (The "Why")**: Briefly explain the business logic, expected UX behavior, or why this code exists (e.g., "Mục đích: Chặn user sử dụng extension nếu chưa đồng ý Privacy").
+2. **AI Code-Level Details (The "How")**:
+   - File paths and specific UI components to create/modify.
+   - Database tables, columns, and Zod/Type schemas (e.g., `Update users.consent_version`).
+   - API payloads, routes, and JSON contracts.
+   - Edge cases, error handling, and exact validation thresholds (e.g., `Return 403 if invalid`).
+
+**Rationale**: Humans review tasks to verify business requirements are met; AI Coders (like god-developer or ck) read tasks to write explicit code. If you only write business jargon, the AI hallucinates. If you only write code names, the human reviewer cannot verify the business value. You MUST provide both.
 
 ### 2. Task Integration & Progression