@kody-ade/kody-engine-lite 0.1.108 → 0.1.110

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kody-ade/kody-engine-lite",
-  "version": "0.1.108",
+  "version": "0.1.110",
   "description": "Autonomous SDLC pipeline: Kody orchestration + Claude Code + LiteLLM",
   "license": "MIT",
   "type": "module",

package/prompts/taskify-ticket.md

@@ -0,0 +1,112 @@
+You are a task decomposition agent. Your job is to break down a product spec into scoped, independently implementable tasks.
+
+## Input
+
+{{#if TICKET_ID}}
+**Mode: ticket**
+
+Use the available MCP tools to fetch ticket **{{TICKET_ID}}**.
+Read everything: title, description, acceptance criteria, sub-tasks, linked issues, attachments.
+{{/if}}
+
+{{#if FILE_CONTENT}}
+**Mode: file**
+
+The product spec is provided below:
+
+```
+{{FILE_CONTENT}}
+```
+{{/if}}
+
+{{#if PROJECT_CONTEXT}}
+## Existing codebase
+
+Use this to avoid suggesting things that already exist and to follow established conventions.
+
+{{PROJECT_CONTEXT}}
+{{/if}}
+
+## Decomposition rules
+
+Break the spec into implementation tasks where each task:
+- Can be implemented and reviewed independently in a single PR
+- Has clear, testable acceptance criteria
+- Contains all the context a developer needs — no references back to the original ticket
+- Is labeled appropriately (e.g. "frontend", "backend", "database", "infra")
+
+Each task body must follow this structure:
+```
+## Context
+Why this task exists and how it fits the bigger picture.
+## Acceptance Criteria
+Bulleted list of what "done" looks like.
+## Test Strategy
+What to test and how — unit tests, integration tests, manual verification steps.
+```
+
+Sizing guide:
+- A task touching 1–3 files with clear requirements = right size
+- A task requiring design decisions or touching many subsystems = too large, split it
+- A task that is just a config change or a one-liner = too small, merge with a related task
+
+Priority guidance — assign `priority` to each task:
+- `high` — blocks other tasks or delivers the ticket's core value
+- `medium` — important but not blocking
+- `low` — polish, edge cases, nice-to-have
+
+Dependency guidance — use `dependsOn` to express ordering:
+- If implementing task B requires task A's code to exist first, set `dependsOn: [indexOfA]` (0-based index into the tasks array).
+- If a task has no dependencies, omit `dependsOn` or use `[]`.
+
+{{#if FEEDBACK}}
+## Answers to previous questions
+
+The product team has provided the following answers:
+
+{{FEEDBACK}}
+
+Use these answers to resolve any previous ambiguities. Do NOT ask questions again — proceed directly to task decomposition.
+{{/if}}
+
+## Output
+
+Write ONLY to: `{{TASK_DIR}}/taskify-result.json`
+
+Do not write any other files. Do not print anything to stdout.
+
+The file must be valid JSON matching exactly one of these two schemas:
+
+**Schema A — tasks ready:**
+```json
+{
+  "status": "ready",
+  "tasks": [
+    {
+      "title": "string (max 72 chars, actionable verb phrase e.g. 'Add OAuth login with Google')",
+      "body": "string (full markdown spec with required sections: ## Context, ## Acceptance Criteria, ## Test Strategy)",
+      "labels": ["optional", "array", "of", "label", "strings"],
+      "priority": "high | medium | low",
+      "dependsOn": [0, 2]
+    }
+  ]
+}
+```
+
+**Schema B — clarifications needed:**
+```json
+{
+  "status": "questions",
+  "questions": ["string", "..."]
+}
+```
+
+Rules:
+- Maximum 3 questions. Only ask what genuinely cannot be determined from the spec.
+- Task titles must be actionable verb phrases ("Add X", "Fix Y", "Implement Z", "Migrate X to Y").
+- Each task body must be self-contained and include ## Context, ## Acceptance Criteria, and ## Test Strategy sections.
+- Labels are for categorization only — not implementation details.
+- `priority` must be one of: `high`, `medium`, `low`.
+- `dependsOn` uses 0-based indices into the tasks array. Omit or use `[]` if there are no dependencies.
+- If the spec is already small enough for a single PR, output one task.
+- Maximum 20 tasks. Consolidate related ones if needed.

package/templates/kody.yml

@@ -64,6 +64,8 @@ jobs:
       pr_number: ${{ steps.parse.outputs.pr_number }}
       feedback: ${{ steps.parse.outputs.feedback }}
       ci_run_id: ${{ steps.parse.outputs.ci_run_id }}
+      ticket_id: ${{ steps.parse.outputs.ticket_id }}
+      prd_file: ${{ steps.parse.outputs.prd_file }}
       dry_run: ${{ steps.parse.outputs.dry_run }}
       valid: ${{ steps.parse.outputs.valid }}
     steps:
@@ -190,12 +192,22 @@ jobs:
           FEEDBACK: ${{ github.event.inputs.feedback || needs.parse.outputs.feedback }}
           COMPLEXITY: ${{ needs.parse.outputs.complexity }}
           CI_RUN_ID: ${{ needs.parse.outputs.ci_run_id }}
+          TICKET_ID: ${{ needs.parse.outputs.ticket_id }}
+          PRD_FILE: ${{ needs.parse.outputs.prd_file }}
           DRY_RUN: ${{ github.event.inputs.dry_run || needs.parse.outputs.dry_run || 'false' }}
           RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
         run: |
           if [ "$MODE" = "bootstrap" ]; then
             echo "Running bootstrap..."
             npx kody-engine-lite bootstrap
+          elif [ "$MODE" = "taskify" ]; then
+            echo "Running taskify..."
+            ARGS=""
+            [ -n "$TICKET_ID" ] && ARGS="$ARGS --ticket $TICKET_ID"
+            [ -n "$PRD_FILE" ] && ARGS="$ARGS --file $PRD_FILE"
+            [ -n "$ISSUE_NUMBER" ] && ARGS="$ARGS --issue-number $ISSUE_NUMBER"
+            [ -n "$TASK_ID" ] && ARGS="$ARGS --task-id $TASK_ID"
+            npx kody-engine-lite taskify $ARGS
           else
             CMD="run"
             [ "$MODE" = "rerun" ] && CMD="rerun"