@nockdev/awf 6.2.5 → 6.2.7

package/.agent/templates/chains/feature/step2-design.md

@@ -0,0 +1,75 @@
+# Feature Chain — Step 2: Design
+
+> Architecture decisions before code
+
+---
+
+## Context
+
+Requirements approved. Now design the solution architecture.
+
+## Input
+
+```
+{{REQUIREMENTS_OUTPUT}}
+{{CODEBASE_CONTEXT}}
+```
+
+## Task
+
+### 1. Architecture Overview
+
+- How does this feature fit into existing architecture?
+- What patterns to follow? (check existing code via `hsa_get_context`)
+- Any new components or modules needed?
+
+### 2. Data Models
+
+```
+// Define new or modified data structures
+// Include types, interfaces, DB schemas
+```
+
+### 3. API Design (if applicable)
+
+| Method | Endpoint         | Request    | Response   | Auth |
+| ------ | ---------------- | ---------- | ---------- | ---- |
+| POST   | `/api/v1/{name}` | `{schema}` | `{schema}` | Yes  |
+
+### 4. Architecture Decision Records (ADR)
+
+| ID     | Decision           | Rationale | Alternatives Considered |
+| ------ | ------------------ | --------- | ----------------------- |
+| DD-001 | [What was decided] | [Why]     | [Other options]         |
+
+### 5. Risk Assessment
+
+| Risk          | Impact   | Likelihood | Mitigation |
+| ------------- | -------- | ---------- | ---------- |
+| [Description] | High/Med | Med/Low    | [Strategy] |
+
+## Output Format
+
+```yaml
+design:
+  architecture: "[Overview]"
+  patterns: ["[Pattern 1]", "[Pattern 2]"]
+  data_models:
+    - name: "[Model]"
+      fields: ["[field: type]"]
+  apis:
+    - method: "POST"
+      path: "/api/v1/{name}"
+      auth: true
+  decisions:
+    - id: "DD-001"
+      decision: "[Choice]"
+      rationale: "[Why]"
+  risks:
+    - risk: "[Description]"
+      mitigation: "[Strategy]"
+```
+
+---
+
+_Chain Step 2 of 5 • Output: design_

package/.agent/templates/chains/feature/step3-planning.md

@@ -0,0 +1,81 @@
+# Feature Chain — Step 3: Planning
+
+> Task breakdown with full traceability
+
+---
+
+## Context
+
+Design complete. Break down into executable tasks.
+
+## Input
+
+```
+{{REQUIREMENTS_OUTPUT}}
+{{DESIGN_OUTPUT}}
+```
+
+## Task
+
+### 1. Task Breakdown
+
+| ID    | Task               | Ref    | Est. | Deps  | Status |
+| ----- | ------------------ | ------ | ---- | ----- | ------ |
+| T-001 | [Task description] | AC-001 | S    | —     | ⬜     |
+| T-002 | [Task description] | AC-001 | M    | T-001 | ⬜     |
+| T-003 | [Task description] | AC-002 | S    | —     | ⬜     |
+
+> Every task MUST reference an AC-xxx. Orphan tasks = scope creep.
+
+### 2. Dependency Graph
+
+```mermaid
+graph LR
+    T-001 --> T-002
+    T-002 --> T-004
+    T-003 --> T-004
+    T-004 --> T-005["Test & Verify"]
+```
+
+### 3. Effort Summary
+
+| Size  | Count | Total Est. |
+| ----- | ----- | ---------- |
+| XS    | N     | Xh         |
+| S     | N     | Xh         |
+| M     | N     | Xh         |
+| **Σ** |       | **Xh**     |
+
+> Include buffer: testing (+20%), review (+10%)
+
+### 4. Milestones
+
+- [ ] **M1**: Core logic complete (T-001..T-003)
+- [ ] **M2**: Tests passing, coverage met (T-004)
+- [ ] **M3**: Documentation updated (T-005)
+
+## Output Format
+
+```yaml
+planning:
+  tasks:
+    - id: "T-001"
+      title: "[Task]"
+      ref: "AC-001"
+      effort: "S"
+      deps: []
+    - id: "T-002"
+      title: "[Task]"
+      ref: "AC-001"
+      effort: "M"
+      deps: ["T-001"]
+  total_effort: "Xh"
+  milestones:
+    - id: "M1"
+      name: "[Name]"
+      tasks: ["T-001", "T-002", "T-003"]
+```
+
+---
+
+_Chain Step 3 of 5 • Output: planning → ⛔ STOP for approval_

package/.agent/templates/chains/feature/step4-implementation.md

@@ -0,0 +1,74 @@
+# Feature Chain — Step 4: Implementation
+
+> Execute with traceability, log every decision
+
+---
+
+## Context
+
+Plan approved. Implement tasks following the breakdown.
+
+## Input
+
+```
+{{PLANNING_OUTPUT}}
+{{DESIGN_OUTPUT}}
+```
+
+## Task
+
+### 1. Execute Tasks
+
+For each task in the plan:
+
+- Reference task ID: `// T-001: [description]`
+- Follow design decisions (DD-xxx)
+- Use existing patterns detected by HSA
+- Run `hsa_check_changes` after each milestone
+
+### 2. Log Files Changed
+
+| File               | Action | Task  | Description            |
+| ------------------ | ------ | ----- | ---------------------- |
+| `path/to/file.ts`  | New    | T-001 | [What was created]     |
+| `path/to/other.ts` | Modify | T-002 | [What changed and why] |
+
+### 3. Decision Log
+
+| Date       | Decision           | Context             | Task  |
+| ---------- | ------------------ | ------------------- | ----- |
+| YYYY-MM-DD | [What was decided] | [Why at this point] | T-001 |
+
+### 4. Progress Tracking
+
+```
+████████░░ 80% (8/10 tasks)
+```
+
+- [x] T-001: Completed
+- [x] T-002: Completed
+- [/] T-003: In progress
+- [ ] T-004: Not started
+
+## Output Format
+
+```yaml
+implementation:
+  files_changed:
+    - path: "path/to/file.ts"
+      action: "new"
+      task: "T-001"
+  decisions:
+    - date: "YYYY-MM-DD"
+      decision: "[Choice]"
+      task: "T-001"
+  progress:
+    completed: ["T-001", "T-002"]
+    in_progress: ["T-003"]
+    remaining: ["T-004"]
+    percentage: 80
+```
+
+---
+
+_Chain Step 4 of 5 • Output: implementation log_

package/.agent/templates/chains/feature/step5-testing.md

@@ -0,0 +1,81 @@
+# Feature Chain — Step 5: Testing & Ship
+
+> Verify all ACs met, then ship
+
+---
+
+## Context
+
+Implementation complete. Verify quality and ship.
+
+## Input
+
+```
+{{IMPLEMENTATION_OUTPUT}}
+{{REQUIREMENTS_OUTPUT}}
+```
+
+## Task
+
+### 1. Test Strategy
+
+| Type        | Scope                 | Framework   | Target         |
+| ----------- | --------------------- | ----------- | -------------- |
+| Unit        | Core logic            | Auto-detect | 80%+ coverage  |
+| Integration | Component interaction | Auto-detect | Key paths      |
+| E2E         | User flows (if UI)    | Auto-detect | Critical paths |
+
+### 2. Test Cases (Traceable)
+
+| ID     | Case          | Covers | Type        | Status |
+| ------ | ------------- | ------ | ----------- | ------ |
+| TC-001 | [Description] | AC-001 | Unit        | ⬜     |
+| TC-002 | [Description] | AC-002 | Integration | ⬜     |
+
+> Every AC-xxx MUST have at least one TC-xxx. Uncovered AC = incomplete.
+
+### 3. Coverage Results
+
+| Metric          | Target | Actual | Status |
+| --------------- | ------ | ------ | ------ |
+| Line Coverage   | 80%    | _TBD_  | ⬜     |
+| Branch Coverage | 70%    | _TBD_  | ⬜     |
+| AC Coverage     | 100%   | _TBD_  | ⬜     |
+
+### 4. AC Verification Matrix
+
+| AC     | Test(s) | Pass | Notes       |
+| ------ | ------- | ---- | ----------- |
+| AC-001 | TC-001  | ⬜   | [Any notes] |
+| AC-002 | TC-002  | ⬜   | [Any notes] |
+
+### 5. Ship Checklist
+
+- [ ] All tests pass
+- [ ] All ACs verified
+- [ ] Coverage targets met
+- [ ] Design docs updated with final state
+- [ ] Implementation log complete
+- [ ] No regressions (existing tests still pass)
+- [ ] Run `/verify` for final gate
+
+## Output Format
+
+```yaml
+testing:
+  test_cases:
+    - id: "TC-001"
+      case: "[Description]"
+      covers: "AC-001"
+      type: "unit"
+      result: "pass"
+  coverage:
+    line: 85
+    branch: 72
+    ac: 100
+  ship_ready: true
+```
+
+---
+
+_Chain Step 5 of 5 • Output: testing results + ship decision_

package/.agent/templates/debug-report.md

@@ -1,6 +1,6 @@
 ---
 name: debug-report
-version: "6.2.5"
+version: "6.2.7"
 type: report
 triggers: ["/debug"]
 ---

package/.agent/templates/deploy-plan.md

@@ -1,6 +1,6 @@
 ---
 name: deploy-plan
-version: "6.2.5"
+version: "6.2.7"
 type: plan
 triggers: ["/deploy"]
 ---

package/.agent/templates/doc-template.md

@@ -1,6 +1,6 @@
 ---
 name: doc-template
-version: "6.2.5"
+version: "6.2.7"
 type: wizard
 triggers: ["/doc", "/generate"]
 ---

package/.agent/templates/feature-lifecycle.md

@@ -0,0 +1,53 @@
+# Feature Lifecycle Template — DOMYH v6.2.7
+
+> **Mục đích**: Template chuẩn cho feature docs khi sử dụng `/feature`
+> **Tạo bởi**: Agent tự động tạo theo feature workflow
+
+---
+
+## 🏗️ Feature: {{FEATURE_NAME}}
+
+**Status**: ⬜ Requirements | 🟡 Design | 🔵 Planning | 🟢 Implementation | ✅ Ship
+**Created**: {{DATE}}
+**Slug**: `{{FEATURE_SLUG}}`
+
+---
+
+## 📊 Phase Progress
+
+| Phase             | Status | Gate          | Document            |
+| ----------------- | ------ | ------------- | ------------------- |
+| 1. Requirements   | ⬜     | G1 (Approval) | `requirements.md`   |
+| 2. Design         | ⬜     | —             | `design.md`         |
+| 3. Planning       | ⬜     | G2 (Approval) | `planning.md`       |
+| 4. Implementation | ⬜     | —             | `implementation.md` |
+| 5. Testing        | ⬜     | G3 (ACs pass) | `testing.md`        |
+
+---
+
+## 📋 Traceability
+
+| AC     | Task(s) | File(s)     | Test(s) | Status |
+| ------ | ------- | ----------- | ------- | ------ |
+| AC-001 | T-001   | `file:line` | TC-001  | ⬜     |
+
+---
+
+## 📝 Summary
+
+{Tóm tắt feature khi hoàn thành}
+
+---
+
+## 📊 Metrics
+
+```yaml
+total_effort: "Xh estimated / Yh actual"
+files_changed: N
+tests_added: N
+coverage: "X%"
+```
+
+---
+
+_Feature Lifecycle • DOMYH Awesome Code v6.2.7_

package/.agent/templates/index.yaml

@@ -2,7 +2,7 @@
 # Template Index — HSA Semantic Template Matching
 # =============================================================================
 # DOMYH Awesome Code Agent — Template Registry for HSA
-# version: 6.2.3
+# version: 6.2.7
 # =============================================================================
 
 templates:
@@ -114,6 +114,19 @@ templates:
     category: testing
     priority: 100
 
+  # ==========================================================================
+  # Feature Lifecycle Templates
+  # ==========================================================================
+  - id: feature-lifecycle
+    file: feature-lifecycle.md
+    name: Feature Lifecycle
+    description: Full feature lifecycle template with phase tracking and traceability
+    keywords:
+      [feature, lifecycle, requirements, design, plan, implement, sdlc, spec]
+    workflows: ["/feature"]
+    category: planning
+    priority: 100
+
 # =============================================================================
 # Workflow Chains (Multi-Step Prompts)
 # =============================================================================
@@ -219,6 +232,44 @@ chains:
         depends_on: impl-3
         description: Add documentation
 
+  /feature:
+    name: Feature Lifecycle Chain
+    description: Spec-driven 5-step feature development with phase gates
+    steps:
+      - order: 1
+        id: feat-1
+        name: Requirements
+        file: chains/feature/step1-requirements.md
+        description: Define problem, user stories, acceptance criteria
+
+      - order: 2
+        id: feat-2
+        name: Design
+        file: chains/feature/step2-design.md
+        depends_on: feat-1
+        description: Architecture decisions, data models, API design
+
+      - order: 3
+        id: feat-3
+        name: Planning
+        file: chains/feature/step3-planning.md
+        depends_on: feat-2
+        description: Task breakdown with traceability
+
+      - order: 4
+        id: feat-4
+        name: Implementation
+        file: chains/feature/step4-implementation.md
+        depends_on: feat-3
+        description: Execute tasks per plan with decision logging
+
+      - order: 5
+        id: feat-5
+        name: Testing & Ship
+        file: chains/feature/step5-testing.md
+        depends_on: feat-4
+        description: Verify all ACs met, coverage check, ship
+
 # =============================================================================
 # Search Configuration
 # =============================================================================
@@ -236,4 +287,4 @@ search:
 # =============================================================================
 # Footer
 # =============================================================================
-# _DOMYH Awesome Code • Template Index v6.2.5 • HSA Integration_
+# _DOMYH Awesome Code • Template Index v6.2.7 • HSA Integration_

package/.agent/templates/migrate-plan.md

@@ -1,6 +1,6 @@
 ---
 name: migrate-plan
-version: "6.2.5"
+version: "6.2.7"
 type: plan
 triggers: ["/migrate"]
 ---

package/.agent/templates/phase-template.md

@@ -1,4 +1,4 @@
-# 📋 Phase Template — DOMYH v6.2.5
+# 📋 Phase Template — DOMYH v6.2.7
 
 > **Mục đích**: Template chuẩn cho phase files khi sử dụng `/plan full`
 > **Tạo bởi**: Agent tự động tạo theo complexity detection

package/.agent/templates/tasks/audit.yaml

@@ -8,7 +8,7 @@
 
 ```yaml
 task_type: audit
-version: "6.2.5"
+version: "6.2.7"
 
 # Required fields
 scope: string              # What to audit

package/.agent/templates/tasks/bug_fix.yaml

@@ -8,7 +8,7 @@
 
 ```yaml
 task_type: bug_fix
-version: "6.2.5"
+version: "6.2.7"
 
 # Required fields
 symptom: string              # What's the visible problem

package/.agent/templates/tasks/code_implementation.yaml

@@ -8,7 +8,7 @@
 
 ```yaml
 task_type: code_implementation
-version: "6.2.5"
+version: "6.2.7"
 
 # Required fields
 description: string       # What to build

package/.agent/templates/tasks/feature_development.yaml

@@ -0,0 +1,89 @@
+# Feature Development Task Template
+
+> Structured template for feature lifecycle tasks
+
+---
+
+## Schema
+
+```yaml
+task_type: feature_development
+version: "6.2.7"
+
+# Required fields
+feature_name: string        # Feature name
+description: string          # What to build
+user_stories: list           # INVEST user stories
+
+# Optional fields
+acceptance_criteria: list    # AC-xxx with priorities
+constraints: list            # Limitations or requirements
+priority: enum               # [P0, P1, P2, P3]
+estimated_effort: string     # [XS, S, M, L, XL, XXL]
+design_decisions: list       # DD-xxx records
+```
+
+---
+
+## Example Task
+
+```yaml
+task:
+  type: feature_development
+
+  feature_name: "JWT Authentication"
+
+  description: |
+    Implement a complete JWT authentication flow
+    with login, logout, token refresh, and role-based access.
+
+  user_stories:
+    - as: "API consumer"
+      want: "authenticate with email/password"
+      so_that: "I can access protected endpoints"
+    - as: "authenticated user"
+      want: "refresh my expired token"
+      so_that: "I don't need to re-login"
+
+  acceptance_criteria:
+    - id: "AC-001"
+      criterion: "Login returns valid JWT on correct credentials"
+      priority: P0
+    - id: "AC-002"
+      criterion: "Invalid credentials return 401"
+      priority: P0
+    - id: "AC-003"
+      criterion: "Expired tokens are rejected and return 401"
+      priority: P0
+    - id: "AC-004"
+      criterion: "Refresh generates new valid token"
+      priority: P1
+
+  constraints:
+    - "Use bcrypt for password hashing"
+    - "JWT expiry: 24 hours"
+    - "Must work with existing User model"
+    - "No breaking changes to existing API"
+
+  priority: P1
+  estimated_effort: M
+
+  design_decisions:
+    - id: "DD-001"
+      decision: "Use HS256 for JWT signing"
+      rationale: "Simpler than RS256 for single-service"
+```
+
+---
+
+## Workflow Integration
+
+This task type triggers:
+- **Persona:** Developer → Architect (design) → Tester (verification)
+- **Chain:** feature (1_requirements → 2_design → 3_planning → 4_implementation → 5_testing)
+- **Phase Gates:** G1 (requirements approval), G2 (plan approval), G3 (AC verification)
+- **Reflection:** Pre-output critic check at each gate
+
+---
+
+_DOMYH Awesome Code • Feature Development Task Template_

package/.agent/templates/tasks/refactor.yaml

@@ -8,7 +8,7 @@
 
 ```yaml
 task_type: refactor
-version: "6.2.5"
+version: "6.2.7"
 
 # Required fields
 target: string            # What to refactor

package/.agent/templates/test-report.md

@@ -1,6 +1,6 @@
 ---
 name: test-report
-version: "6.2.5"
+version: "6.2.7"
 type: report
 triggers: ["/test"]
 ---