smart-spec-kit-mcp 2.2.8 → 2.3.0

package/dist/schemas/workflowSchema.d.ts

@@ -19,7 +19,11 @@ export declare const WorkflowStepSchema: z.ZodObject<{
     }>;
     description: z.ZodString;
     agent: z.ZodOptional<z.ZodString>;
-    inputs: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>;
+    inputs: z.ZodOptional<z.ZodUnion<readonly [z.ZodArray<z.ZodObject<{
+        name: z.ZodString;
+        description: z.ZodOptional<z.ZodString>;
+        required: z.ZodOptional<z.ZodBoolean>;
+    }, z.core.$strip>>, z.ZodRecord<z.ZodString, z.ZodUnion<readonly [z.ZodString, z.ZodArray<z.ZodString>]>>]>>;
     outputs: z.ZodOptional<z.ZodArray<z.ZodString>>;
     next: z.ZodOptional<z.ZodString>;
 }, z.core.$strip>;
@@ -59,7 +63,11 @@ export declare const WorkflowSchema: z.ZodObject<{
         }>;
         description: z.ZodString;
         agent: z.ZodOptional<z.ZodString>;
-        inputs: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>;
+        inputs: z.ZodOptional<z.ZodUnion<readonly [z.ZodArray<z.ZodObject<{
+            name: z.ZodString;
+            description: z.ZodOptional<z.ZodString>;
+            required: z.ZodOptional<z.ZodBoolean>;
+        }, z.core.$strip>>, z.ZodRecord<z.ZodString, z.ZodUnion<readonly [z.ZodString, z.ZodArray<z.ZodString>]>>]>>;
         outputs: z.ZodOptional<z.ZodArray<z.ZodString>>;
         next: z.ZodOptional<z.ZodString>;
     }, z.core.$strip>>;

package/dist/schemas/workflowSchema.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"workflowSchema.d.ts","sourceRoot":"","sources":["../../src/schemas/workflowSchema.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;GAEG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;iBAU7B,CAAC;AAEH;;GAEG;AACH,eAAO,MAAM,sBAAsB;;;;;iBAKjC,CAAC;AAEH;;GAEG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAQzB,CAAC;AAGH,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAC9D,MAAM,MAAM,gBAAgB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,sBAAsB,CAAC,CAAC;AACtE,MAAM,MAAM,QAAQ,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAC"}
+{"version":3,"file":"workflowSchema.d.ts","sourceRoot":"","sources":["../../src/schemas/workflowSchema.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AA2BxB;;GAEG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;iBAU7B,CAAC;AAEH;;GAEG;AACH,eAAO,MAAM,sBAAsB;;;;;iBAKjC,CAAC;AAEH;;GAEG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAQzB,CAAC;AAGH,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAC9D,MAAM,MAAM,gBAAgB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,sBAAsB,CAAC,CAAC;AACtE,MAAM,MAAM,QAAQ,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAC"}

package/dist/schemas/workflowSchema.js

@@ -4,6 +4,28 @@
  * Zod schemas for validating workflow YAML files
  */
 import { z } from "zod";
+/**
+ * Schema for input parameter (flexible format)
+ */
+const InputItemSchema = z.object({
+    name: z.string(),
+    description: z.string().optional(),
+    required: z.boolean().optional(),
+});
+/**
+ * Flexible input value: can be string or array of strings
+ */
+const FlexibleInputValue = z.union([
+    z.string(),
+    z.array(z.string()),
+]);
+/**
+ * Flexible inputs: can be array of objects or key-value record with flexible values
+ */
+const FlexibleInputsSchema = z.union([
+    z.array(InputItemSchema),
+    z.record(z.string(), FlexibleInputValue),
+]).optional();
 /**
  * Schema for a single workflow step
  */
@@ -14,7 +36,7 @@ export const WorkflowStepSchema = z.object({
         .describe("The type of action to perform"),
     description: z.string().describe("Detailed description of what this step does"),
     agent: z.string().optional().describe("Agent to use for this step (e.g., SpecAgent, PlanAgent)"),
-    inputs: z.record(z.string(), z.string()).optional().describe("Input parameters for the step"),
+    inputs: FlexibleInputsSchema.describe("Input parameters for the step"),
     outputs: z.array(z.string()).optional().describe("Expected outputs from this step"),
     next: z.string().optional().describe("Next step ID (if not sequential)"),
 });

package/dist/schemas/workflowSchema.js.map

@@ -1 +1 @@
-{"version":3,"file":"workflowSchema.js","sourceRoot":"","sources":["../../src/schemas/workflowSchema.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;GAEG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,CAAC,MAAM,CAAC;IACzC,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,gCAAgC,CAAC;IACzD,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,0BAA0B,CAAC;IACrD,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,WAAW,EAAE,kBAAkB,EAAE,QAAQ,EAAE,aAAa,EAAE,YAAY,CAAC,CAAC;SACrF,QAAQ,CAAC,+BAA+B,CAAC;IAC5C,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,6CAA6C,CAAC;IAC/E,KAAK,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,yDAAyD,CAAC;IAChG,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,+BAA+B,CAAC;IAC7F,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,iCAAiC,CAAC;IACnF,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,kCAAkC,CAAC;CACzE,CAAC,CAAC;AAEH;;GAEG;AACH,MAAM,CAAC,MAAM,sBAAsB,GAAG,CAAC,CAAC,MAAM,CAAC;IAC7C,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC;IAClC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IAC7B,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IAC9B,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE;CACrC,CAAC,CAAC;AAEH;;GAEG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,CAAC,MAAM,CAAC;IACrC,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,qBAAqB,CAAC;IAChD,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,8BAA8B,CAAC;IAChE,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,iCAAiC,CAAC;IACnE,QAAQ,EAAE,sBAAsB,CAAC,QAAQ,EAAE;IAC3C,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,qDAAqD,CAAC;IACpF,YAAY,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC,QAAQ,CAAC,iCAAiC,CAAC;IACzF,KAAK,EAAE,CAAC,CAAC,KAAK,CAAC,kBAAkB,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC,gCAAgC,CAAC;CACrF,CAAC,CAAC"}
+{"version":3,"file":"workflowSchema.js","sourceRoot":"","sources":["../../src/schemas/workflowSchema.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;GAEG;AACH,MAAM,eAAe,GAAG,CAAC,CAAC,MAAM,CAAC;IAC/B,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE;IAChB,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IAClC,QAAQ,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,QAAQ,EAAE;CACjC,CAAC,CAAC;AAEH;;GAEG;AACH,MAAM,kBAAkB,GAAG,CAAC,CAAC,KAAK,CAAC;IACjC,CAAC,CAAC,MAAM,EAAE;IACV,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC;CACpB,CAAC,CAAC;AAEH;;GAEG;AACH,MAAM,oBAAoB,GAAG,CAAC,CAAC,KAAK,CAAC;IACnC,CAAC,CAAC,KAAK,CAAC,eAAe,CAAC;IACxB,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,kBAAkB,CAAC;CACzC,CAAC,CAAC,QAAQ,EAAE,CAAC;AAEd;;GAEG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,CAAC,MAAM,CAAC;IACzC,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,gCAAgC,CAAC;IACzD,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,0BAA0B,CAAC;IACrD,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,WAAW,EAAE,kBAAkB,EAAE,QAAQ,EAAE,aAAa,EAAE,YAAY,CAAC,CAAC;SACrF,QAAQ,CAAC,+BAA+B,CAAC;IAC5C,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,6CAA6C,CAAC;IAC/E,KAAK,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,yDAAyD,CAAC;IAChG,MAAM,EAAE,oBAAoB,CAAC,QAAQ,CAAC,+BAA+B,CAAC;IACtE,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,iCAAiC,CAAC;IACnF,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,kCAAkC,CAAC;CACzE,CAAC,CAAC;AAEH;;GAEG;AACH,MAAM,CAAC,MAAM,sBAAsB,GAAG,CAAC,CAAC,MAAM,CAAC;IAC7C,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC;IAClC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IAC7B,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IAC9B,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE;CACrC,CAAC,CAAC;AAEH;;GAEG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,CAAC,MAAM,CAAC;IACrC,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,qBAAqB,CAAC;IAChD,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,8BAA8B,CAAC;IAChE,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,iCAAiC,CAAC;IACnE,QAAQ,EAAE,sBAAsB,CAAC,QAAQ,EAAE;IAC3C,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,qDAAqD,CAAC;IACpF,YAAY,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC,QAAQ,CAAC,iCAAiC,CAAC;IACzF,KAAK,EAAE,CAAC,CAAC,KAAK,CAAC,kBAAkB,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC,gCAAgC,CAAC;CACrF,CAAC,CAAC"}

package/dist/utils/workflowLoader.d.ts

@@ -51,7 +51,11 @@ export declare function getWorkflowStep(workflow: Workflow, stepId: string): {
     action: "fetch_ado" | "generate_content" | "review" | "create_file" | "call_agent";
     description: string;
     agent?: string | undefined;
-    inputs?: Record<string, string> | undefined;
+    inputs?: Record<string, string | string[]> | {
+        name: string;
+        description?: string | undefined;
+        required?: boolean | undefined;
+    }[] | undefined;
     outputs?: string[] | undefined;
     next?: string | undefined;
 } | undefined;
@@ -64,7 +68,11 @@ export declare function getFirstStep(workflow: Workflow): {
     action: "fetch_ado" | "generate_content" | "review" | "create_file" | "call_agent";
     description: string;
     agent?: string | undefined;
-    inputs?: Record<string, string> | undefined;
+    inputs?: Record<string, string | string[]> | {
+        name: string;
+        description?: string | undefined;
+        required?: boolean | undefined;
+    }[] | undefined;
     outputs?: string[] | undefined;
     next?: string | undefined;
 } | undefined;
@@ -77,7 +85,11 @@ export declare function getNextStep(workflow: Workflow, currentStepId: string):
     action: "fetch_ado" | "generate_content" | "review" | "create_file" | "call_agent";
     description: string;
     agent?: string | undefined;
-    inputs?: Record<string, string> | undefined;
+    inputs?: Record<string, string | string[]> | {
+        name: string;
+        description?: string | undefined;
+        required?: boolean | undefined;
+    }[] | undefined;
     outputs?: string[] | undefined;
     next?: string | undefined;
 } | null | undefined;

package/dist/utils/workflowLoader.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"workflowLoader.d.ts","sourceRoot":"","sources":["../../src/utils/workflowLoader.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAKH,OAAO,EAAkB,KAAK,QAAQ,EAAE,MAAM,8BAA8B,CAAC;AAG7E,YAAY,EAAE,QAAQ,EAAE,MAAM,8BAA8B,CAAC;AAmH7D;;GAEG;AACH,wBAAsB,aAAa,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CAGvD;AAED;;GAEG;AACH,wBAAsB,qBAAqB,IAAI,OAAO,CACpD;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,OAAO,GAAG,SAAS,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,EAAE,CAC9D,CAEA;AAED;;GAEG;AACH,wBAAsB,YAAY,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,QAAQ,CAAC,CA8B1E;AAED;;GAEG;AACH,wBAAsB,YAAY,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAaxE;AAED;;GAEG;AACH,wBAAsB,aAAa,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CAGvD;AAED;;GAEG;AACH,wBAAsB,wBAAwB,CAC5C,YAAY,EAAE,MAAM,GACnB,OAAO,CAAC;IAAE,QAAQ,EAAE,QAAQ,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,CAAC,CAKnD;AAED;;GAEG;AACH,wBAAgB,eAAe,CAAC,QAAQ,EAAE,QAAQ,EAAE,MAAM,EAAE,MAAM;;;;;;;;;cAEjE;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,QAAQ,EAAE,QAAQ;;;;;;;;;cAE9C;AAED;;GAEG;AACH,wBAAgB,WAAW,CAAC,QAAQ,EAAE,QAAQ,EAAE,aAAa,EAAE,MAAM;;;;;;;;;qBAepE;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC,IAAI,CAAC,CAiErD;AAED;;GAEG;AACH,wBAAgB,aAAa,IAAI;IAC/B,WAAW,EAAE,MAAM,CAAC;IACpB,WAAW,EAAE,MAAM,CAAC;IACpB,WAAW,EAAE;QAAE,SAAS,EAAE,MAAM,EAAE,CAAC;QAAC,SAAS,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC;CAC3D,CASA"}
+{"version":3,"file":"workflowLoader.d.ts","sourceRoot":"","sources":["../../src/utils/workflowLoader.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAKH,OAAO,EAAkB,KAAK,QAAQ,EAAE,MAAM,8BAA8B,CAAC;AAG7E,YAAY,EAAE,QAAQ,EAAE,MAAM,8BAA8B,CAAC;AAmH7D;;GAEG;AACH,wBAAsB,aAAa,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CAGvD;AAED;;GAEG;AACH,wBAAsB,qBAAqB,IAAI,OAAO,CACpD;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,OAAO,GAAG,SAAS,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,EAAE,CAC9D,CAEA;AAED;;GAEG;AACH,wBAAsB,YAAY,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,QAAQ,CAAC,CA8B1E;AAED;;GAEG;AACH,wBAAsB,YAAY,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAaxE;AAED;;GAEG;AACH,wBAAsB,aAAa,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CAGvD;AAED;;GAEG;AACH,wBAAsB,wBAAwB,CAC5C,YAAY,EAAE,MAAM,GACnB,OAAO,CAAC;IAAE,QAAQ,EAAE,QAAQ,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,CAAC,CAKnD;AAED;;GAEG;AACH,wBAAgB,eAAe,CAAC,QAAQ,EAAE,QAAQ,EAAE,MAAM,EAAE,MAAM;;;;;;;;;;;;;cAEjE;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,QAAQ,EAAE,QAAQ;;;;;;;;;;;;;cAE9C;AAED;;GAEG;AACH,wBAAgB,WAAW,CAAC,QAAQ,EAAE,QAAQ,EAAE,aAAa,EAAE,MAAM;;;;;;;;;;;;;qBAepE;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC,IAAI,CAAC,CAiErD;AAED;;GAEG;AACH,wBAAgB,aAAa,IAAI;IAC/B,WAAW,EAAE,MAAM,CAAC;IACpB,WAAW,EAAE,MAAM,CAAC;IACpB,WAAW,EAAE;QAAE,SAAS,EAAE,MAAM,EAAE,CAAC;QAAC,SAAS,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC;CAC3D,CASA"}

package/docs/DOCUMENTATION.md

@@ -369,25 +369,36 @@ Then use: `speckit: validate my-custom`
 **Examples**:
 
 ```text
-speckit: workflow list
-speckit: workflow start feature-standard
-speckit: workflow start bugfix MyBug auto
-speckit: workflow status
+/speckit.workflow feature-standard Multi-View
+/speckit.workflow feature-quick
+/speckit.workflow bugfix
 /speckit.workflow list
+/speckit.workflow status
 ```
 
+**Simplified Usage**:
+
+Just type the workflow name after `/speckit.workflow`:
+
+- `/speckit.workflow feature-standard` → Starts the standard workflow
+- `/speckit.workflow bugfix` → Starts the bugfix workflow
+- Any text after the workflow name becomes the `contextId`
+
 **Behavior**:
 
 **Action: list**
+
 1. Scans `.spec-kit/workflows/` (local) and `starter-kit/workflows/` (built-in)
 2. Displays table with workflow name, description, and source (🔧 Local / 📦 Built-in)
 
 **Action: start**
+
 1. Validates workflow exists
-2. Provides instructions to call `start_workflow` MCP tool
+2. Calls `start_workflow` MCP tool to begin the workflow
 3. Workflow will guide through each step automatically
 
 **Action: status**
+
 1. Checks active workflow session
 2. Shows current step, completed actions, next required action
 
@@ -395,9 +406,9 @@ speckit: workflow status
 
 | Workflow | Description | Steps |
 |----------|-------------|-------|
-| `feature-quick` | Quick feature implementation | specify → implement (lightweight) |
-| `feature-standard` | Standard feature workflow | specify → plan → tasks → implement |
-| `feature-full` | Full feature with validation | specify → plan → tasks → implement → validate |
+| `feature-quick` | Quick feature implementation | spec → implement |
+| `feature-standard` | Standard feature workflow | spec → plan → tasks → implement |
+| `feature-full` | Full feature with validation | spec → security review → RGPD review → plan → tasks → implement |
 | `bugfix` | Bug fix with reproduction | reproduce → analyze → fix → test |
 
 **Creating Custom Workflows**:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "smart-spec-kit-mcp",
-  "version": "2.2.8",
+  "version": "2.3.0",
   "description": "AI-driven specification platform using MCP (Model Context Protocol) for VS Code & GitHub Copilot",
   "main": "dist/index.js",
   "type": "module",

package/starter-kit/copilot-instructions.md

@@ -15,6 +15,7 @@ Users can type `/speckit.` to see available slash commands:
 | `/speckit.clarify` | `speckit_clarify` | Clarify requirements |
 | `/speckit.validate` | `speckit_validate` | Validate compliance (security, RGPD, etc.) |
 | `/speckit.memory` | `speckit_memory` | Manage project memory |
+| `/speckit.workflow` | `start_workflow` | Start an automated workflow |
 | `/speckit.help` | `speckit_help` | Get help and documentation |
 
 ## Keyword Commands (Alternative)
@@ -30,6 +31,7 @@ When the user mentions **"speckit:"** followed by a command, or uses these keywo
 | `speckit: clarify`, `clarifier`, `préciser` | `speckit_clarify` | Clarify requirements |
 | `speckit: validate`, `valider`, `vérifier` | `speckit_validate` | Validate compliance (security, RGPD, etc.) |
 | `speckit: memory`, `enrichir la mémoire`, `ajouter au contexte` | `speckit_memory` | Manage project memory |
+| `speckit: workflow feature-standard`, `démarrer workflow` | `start_workflow` | Start an automated workflow |
 | `speckit: help`, `aide sur speckit`, questions about spec-kit | `speckit_help` | Get help and documentation |
 
 ## Getting Help
@@ -113,21 +115,28 @@ After calling a spec-kit tool, follow the instructions in the tool response. The
 - Specific instructions for what to generate
 - Suggested next step
 
-## Automated Workflows (Optional)
+## Automated Workflows
 
-For multi-step automation, use `start_workflow`:
+Workflows automate multi-step processes. Use `/speckit.workflow` or `start_workflow`:
 
-| User Says | Action |
-|-----------|--------|
-| `speckit: start_workflow workflow_name="feature-quick"` | Start quick feature workflow (lightweight) |
-| `speckit: start_workflow workflow_name="feature-standard" PiP Support` | Start feature workflow for PiP Support |
-| `speckit: start_workflow workflow_name="bugfix" auto=true` | Start bugfix workflow in AUTO mode |
+| Workflow | Description |
+|----------|-------------|
+| `feature-quick` | Quick win: spec → implement |
+| `feature-standard` | Standard: spec → plan → tasks → implement |
+| `feature-full` | Complete with security/RGPD validations |
+| `bugfix` | Bug fix with reproduction |
 
-**Auto Mode** (`auto=true`): Proceeds through all steps without asking for user approval. Default is `false` (manual approval required).
+### Examples
+
+- `/speckit.workflow feature-standard Multi-View` → Start standard workflow for "Multi-View"
+- `/speckit.workflow feature-quick` → Start quick workflow
+- `/speckit.workflow bugfix` → Start bugfix workflow
+
+**Auto Mode**: Add `auto=true` to proceed without approval prompts.
 
 ## Example Interactions
 
-**User**: `/speckit.specify pour un système de notifications push`
+**User**: `/speckit.specify système de notifications push`
 **Action**: Call `speckit_specify` with `requirements: "système de notifications push"`
 
 **User**: `/speckit.plan`  
@@ -139,25 +148,13 @@ For multi-step automation, use `start_workflow`:
 **User**: `/speckit.memory list`
 **Action**: Call `speckit_memory` with `action: "list"`
 
-**User**: `/speckit.memory ajouter une décision technique`
-**Action**: Call `speckit_memory` with `action: "add"`, `category: "decisions"`
-
-**User**: `/speckit.memory auto`
-**Action**: Call `speckit_memory` with `action: "auto"` to auto-enrich from context
-
 **User**: `/speckit.validate security`
 **Action**: Call `speckit_validate` with `ruleType: "security"`
 
-**User**: `/speckit.validate rgpd phase=spec`
-**Action**: Call `speckit_validate` with `ruleType: "rgpd"`, `phase: "spec"`
-
-**User**: `/speckit.validate architecture-rules`
-**Action**: Call `speckit_validate` with `ruleType: "architecture"` (uses custom rules file)
-
-**User**: `speckit: start_workflow workflow_name="feature-standard" PiP Support auto=true`
-**Action**: Call `start_workflow` with `workflow_name: "feature-standard"`, `context_id: "PiP Support"`, `auto: true`
+**User**: `/speckit.workflow feature-standard Multi-View`
+**Action**: Call `start_workflow` with `workflow_name: "feature-standard"`, `context_id: "Multi-View"`
 
-**User**: `/speckit.help comment créer un nouveau workflow ?`
+**User**: `/speckit.help workflows`
 **Action**: Call `speckit_help` with `topic: "workflows"`
 
 **User**: "Comment fonctionne spec-kit ?"

package/starter-kit/github-prompts/speckit.help.prompt.md

@@ -1,46 +1,73 @@
+````prompt
 ---
-description: "Obtenir de l'aide sur l'utilisation de Spec-Kit"
+description: "Afficher l'aide et les commandes Spec-Kit disponibles"
 mode: "agent"
 tools: ["mcp_spec-kit_speckit_help"]
 ---
 
 # Spec-Kit: Aide
 
-Vous utilisez **Spec-Kit** pour obtenir de l'aide sur le framework.
-
-## Instructions
-
-Appelez l'outil MCP `speckit_help` pour obtenir de l'aide.
+## Arguments utilisateur
 
 ```
 $ARGUMENTS
 ```
 
-## Sujets d'aide disponibles
+## Instructions
 
-- **workflows** : Comment créer et personnaliser des workflows
-- **templates** : Comment utiliser et personnaliser les templates
-- **prompts** : Comment modifier les prompts des commandes
-- **customization** : Personnalisation avancée de Spec-Kit
-- **troubleshooting** : Résolution de problèmes courants
+Affiche l'aide Spec-Kit. Si un sujet est fourni, donne des détails sur ce sujet.
 
-## Commandes Spec-Kit
+## 🚀 Commandes Slash Disponibles
 
-| Commande | Description |
+| Commande | Description | Exemple |
+|----------|-------------|---------|
+| `/speckit.specify` | Créer une spécification | `/speckit.specify système de login` |
+| `/speckit.plan` | Créer un plan d'implémentation | `/speckit.plan` |
+| `/speckit.tasks` | Générer les tâches | `/speckit.tasks` |
+| `/speckit.implement` | Implémenter les tâches | `/speckit.implement` ou `/speckit.implement task 3` |
+| `/speckit.clarify` | Clarifier les exigences | `/speckit.clarify` |
+| `/speckit.validate` | Valider conformité (sécurité, RGPD) | `/speckit.validate security` |
+| `/speckit.memory` | Gérer la mémoire projet | `/speckit.memory list` |
+| `/speckit.workflow` | Démarrer un workflow automatisé | `/speckit.workflow feature-standard` |
+| `/speckit.help` | Cette aide | `/speckit.help workflows` |
+
+## 📋 Workflows Automatisés
+
+| Workflow | Description |
 |----------|-------------|
-| `/speckit.specify` | Créer une spécification |
-| `/speckit.plan` | Créer un plan d'implémentation |
-| `/speckit.tasks` | Générer les tâches |
-| `/speckit.implement` | Implémenter les tâches |
-| `/speckit.clarify` | Clarifier les exigences |
-| `/speckit.validate` | Valider la conformité |
-| `/speckit.memory` | Gérer la mémoire projet |
-| `/speckit.help` | Cette aide |
+| `feature-quick` | Rapide: spec → implement |
+| `feature-standard` | Standard: spec → plan → tasks → implement |
+| `feature-full` | Complet avec validations sécurité/RGPD |
+| `bugfix` | Correction de bug |
+
+**Usage:** `/speckit.workflow feature-standard Mon Feature`
 
-## Workflow typique
+## 🔄 Workflow Typique
 
 ```
 specify → plan → tasks → implement
     ↑
   clarify (si nécessaire)
 ```
+
+## 📁 Structure du Projet
+
+```
+.spec-kit/
+├── prompts/      # Personnaliser les commandes
+├── templates/    # Templates des documents
+├── memory/       # Constitution projet
+├── rules/        # Règles de validation
+└── workflows/    # Workflows custom
+specs/            # Specs générées
+```
+
+## 🎯 Sujets d'Aide
+
+- **workflows** : Créer et personnaliser des workflows
+- **templates** : Utiliser et modifier les templates
+- **prompts** : Modifier le comportement des commandes
+- **customization** : Personnalisation avancée
+- **troubleshooting** : Résolution de problèmes
+
+````

package/starter-kit/github-prompts/speckit.workflow.prompt.md

@@ -1,90 +1,48 @@
 ````prompt
 ---
-description: "Gérer les workflows Spec-Kit (lister, démarrer, statut)"
+description: "Démarrer un workflow Spec-Kit automatisé"
 mode: "agent"
-tools: ["mcp_spec-kit_speckit_workflow", "mcp_spec-kit_start_workflow", "mcp_spec-kit_workflow_status"]
+tools: ["mcp_spec-kit_start_workflow", "mcp_spec-kit_workflow_status", "mcp_spec-kit_abort_workflow"]
 ---
 
-# Spec-Kit: Gestion des Workflows
+# Spec-Kit: Workflows
 
-Vous utilisez **Spec-Kit** pour gérer les workflows multi-étapes.
+Démarre un workflow automatisé multi-étapes.
 
-## Instructions
-
-1. **Appeler l'outil MCP** `speckit_workflow` pour gérer les workflows
-2. **Interpréter les arguments** fournis par l'utilisateur
+## Arguments utilisateur
 
 ```
 $ARGUMENTS
 ```
 
-## Actions disponibles
-
-### Lister les workflows
-```
-action: "list"
-```
-
-Affiche tous les workflows disponibles (locaux et intégrés).
-
-### Démarrer un workflow
-```
-action: "start"
-workflow_name: "feature-standard"
-context_id: "MonFeature"      # Optionnel
-auto: false                    # Optionnel (true = automatique)
-```
-
-Démarre un workflow multi-étapes. Le workflow guide automatiquement à travers les étapes.
-
-### Vérifier le statut
-```
-action: "status"
-```
-
-Affiche l'état du workflow actif (étape en cours, actions complétées).
-
-## Workflows intégrés
-
-| Workflow | Description |
-|----------|-------------|
-| `feature-quick` | Feature rapide (léger, sans breakdown de tâches) |
-| `feature-standard` | Feature standard (spec → plan → tasks → implement) |
-| `feature-full` | Feature complète avec validation et tests |
-| `bugfix` | Correction de bug avec reproduction |
+## Comment interpréter
 
-## Exemples d'utilisation
+1. **Si l'utilisateur donne un nom de workflow** → Démarrer ce workflow avec `start_workflow`
+2. **Si l'utilisateur dit "list"** → Lister les workflows disponibles
+3. **Si l'utilisateur dit "status"** → Vérifier le statut avec `workflow_status`
+4. **Si l'utilisateur dit "stop" ou "abort"** → Annuler avec `abort_workflow`
 
-### Utilisateur : "speckit: workflow list"
-→ Appeler `speckit_workflow` avec `action: "list"`
+## Workflows disponibles
 
-### Utilisateur : "speckit: workflow start feature-standard"
-→ Appeler `speckit_workflow` avec `action: "start"`, `workflow_name: "feature-standard"`
+| Nom | Description |
+|-----|-------------|
+| `feature-quick` | Quick win (spec → implement) |
+| `feature-standard` | Standard (spec → plan → tasks → implement) |
+| `feature-full` | Avec validations sécurité/RGPD |
+| `bugfix` | Correction de bug |
 
-### Utilisateur : "speckit: workflow start feature-full MyFeature auto"
-→ Appeler `speckit_workflow` avec:
-- `action: "start"`
-- `workflow_name: "feature-full"`
-- `context_id: "MyFeature"`
-- `auto: true`
+## Exemples
 
-### Utilisateur : "speckit: workflow status"
-→ Appeler `speckit_workflow` avec `action: "status"`
+- `/speckit.workflow feature-standard Multi-View` → `start_workflow` avec `workflow_name="feature-standard"`, `context_id="Multi-View"`
+- `/speckit.workflow list` → Afficher la liste des workflows
+- `/speckit.workflow status` → Vérifier le statut
 
-## Mode automatique
+## Simplification
 
-Par défaut, les workflows demandent une approbation à chaque étape. 
-
-En mode automatique (`auto: true`), le workflow s'exécute sans interruption.
-
-## Workflow typique
-
-```
-specify → plan → tasks → implement
-    ↑
-  clarify (si nécessaire)
-```
+Si l'utilisateur tape juste un nom de workflow sans "start":
+- `/speckit.workflow feature-standard` → Démarrer feature-standard
+- `/speckit.workflow bugfix` → Démarrer bugfix
 
-Les workflows orchestrent ces commandes automatiquement.
+Le texte après le nom du workflow devient le `context_id`.
 
 ````

package/starter-kit/workflows/bugfix.yaml

@@ -1,12 +1,12 @@
 # Bugfix Workflow
-# Streamlined process for bug fixes with validation checkpoints
+# Structured process for bug fixes
 
 name: bugfix
 displayName: "Bug Fix"
 description: "Structured workflow for analyzing, fixing, and validating bug corrections"
 
 metadata:
-  version: "1.0"
+  version: "2.0"
   author: "Spec-Kit"
   tags:
     - bugfix
@@ -17,31 +17,37 @@ template: bugfix-report.md
 defaultAgent: SpecAgent
 
 steps:
+  # Step 1: Analyze Bug
   - id: analyze-bug
-    name: "Analyze Bug & Root Cause"
-    action: fetch_ado
+    name: "1. Analyze Bug"
+    action: call_agent
+    agent: SpecAgent
     description: |
-      Retrieve the bug work item from Azure DevOps and analyze:
-      - Reproduction steps
-      - Error logs and stack traces
-      - Affected components
-      - User impact assessment
+      Analyze the bug based on user description:
+      
+      - Understand the symptoms
+      - Identify reproduction steps
+      - Locate affected components
+      - Determine root cause
       
-      Identify the root cause of the issue.
+      Document findings clearly.
+    inputs:
+      bug_description: "Description from user"
     outputs:
-      - bug_data
       - root_cause_analysis
 
+  # Step 2: Plan Fix
   - id: plan-fix
-    name: "Plan Correction"
+    name: "2. Plan Correction"
     action: call_agent
     agent: PlanAgent
     description: |
-      Create a correction plan including:
+      Create a correction plan:
+      
       - Proposed fix approach
       - Files/components to modify
       - Potential side effects
-      - Rollback strategy if needed
+      - Test cases to verify fix
       
       Keep the fix minimal and focused.
     inputs:
@@ -49,51 +55,36 @@ steps:
     outputs:
       - fix_plan
 
-  - id: security-check
-    name: "Security Validation"
-    action: review
-    agent: GovAgent
-    description: |
-      Quick security review of the proposed fix:
-      - [ ] No new vulnerabilities introduced
-      - [ ] Input validation maintained
-      - [ ] No sensitive data exposure
-      - [ ] Authentication/Authorization intact
-    inputs:
-      document: "fix_plan"
-    outputs:
-      - security_clearance
-
+  # Step 3: Implement Fix
   - id: implement-fix
-    name: "Implement & Test"
-    action: generate_content
+    name: "3. Implement Fix"
+    action: call_agent
+    agent: SpecAgent
     description: |
-      Implement the fix following the plan:
-      1. Write the code fix
-      2. Add unit tests for the bug scenario
-      3. Add regression tests
-      4. Update documentation if needed
+      Implement the bug fix:
       
-      Ensure test coverage for the fixed code path.
+      - Make minimal changes
+      - Follow project conventions
+      - Add/update tests
+      - Document the fix
     inputs:
-      plan: "fix_plan"
+      source: "fix_plan"
     outputs:
-      - code_changes
-      - test_cases
+      - implementation
 
-  - id: final-review
-    name: "Final Review"
+  # Step 4: Verify
+  - id: verify-fix
+    name: "4. Verify Fix"
     action: review
     agent: GovAgent
     description: |
-      Final validation before merge:
-      - [ ] Fix addresses root cause
-      - [ ] No regression introduced
+      Verify the fix is complete:
+      
+      - [ ] Bug is resolved
+      - [ ] No regressions introduced
       - [ ] Tests pass
-      - [ ] Code review approved
-      - [ ] Documentation updated
+      - [ ] No security issues
     inputs:
-      changes: "code_changes"
-      tests: "test_cases"
+      source: "implementation"
     outputs:
-      - approval_status
+      - verification_report

package/starter-kit/workflows/feature-full.yaml

@@ -1,17 +1,17 @@
-# Full Feature Workflow with Governance
-# Complete workflow with all validation checkpoints
+# Feature Full Workflow
+# Complete workflow with validation checkpoints
 
 name: feature-full
-displayName: "Feature with Full Governance"
-description: "Complete feature workflow including RGPD, Security, Architecture, Design System, and Testing validations"
+displayName: "Feature with Validation"
+description: "Complete feature workflow with security and RGPD validations"
 
 metadata:
-  version: "1.0"
+  version: "2.0"
   author: "Spec-Kit"
   tags:
     - feature
     - governance
-    - enterprise
+    - validation
 
 template: functional-spec.md
 defaultAgent: SpecAgent
@@ -20,86 +20,40 @@ steps:
   # ═══════════════════════════════════════════════════════════════
   # PHASE 1: SPECIFICATION
   # ═══════════════════════════════════════════════════════════════
-  
-  - id: fetch-requirements
-    name: "1.1 Fetch Requirements"
-    action: fetch_ado
-    description: |
-      Retrieve the Feature work item and all linked items from Azure DevOps.
-      
-      Extract:
-      - Title and description
-      - Acceptance criteria
-      - Parent Epic context
-      - Linked User Stories
-      - Attachments (mockups, documents)
-    outputs:
-      - workitem_data
-      - linked_items
-      - attachments
 
-  - id: write-spec
-    name: "1.2 Write Functional Specification"
+  - id: create-spec
+    name: "1. Create Specification"
     action: call_agent
     agent: SpecAgent
     description: |
-      Generate a comprehensive functional specification including:
+      Create a comprehensive functional specification.
       
-      **Functional Requirements**
+      Include:
+      - Feature summary and objectives
       - User stories with acceptance criteria
-      - Business rules
+      - Functional requirements
+      - Non-functional requirements
       - Data requirements
+      - Dependencies and constraints
       
-      **Non-Functional Requirements**
-      - Performance targets
-      - Availability requirements
-      - Scalability needs
-      
-      Mark uncertain sections with [TO FILL] for human review.
+      Mark unclear sections with [NEEDS CLARIFICATION] for review.
     inputs:
-      source: "workitem_data"
+      - name: requirements
+        description: "Feature description from user"
+        required: true
     outputs:
-      - functional_spec
+      - spec_document
 
   # ═══════════════════════════════════════════════════════════════
-  # PHASE 2: VALIDATION GATES
+  # PHASE 2: VALIDATION
   # ═══════════════════════════════════════════════════════════════
 
-  - id: rgpd-review
-    name: "2.1 🛡️ RGPD Compliance Review"
-    action: review
-    agent: GovAgent
-    description: |
-      Validate GDPR/RGPD compliance:
-      
-      **Data Collection**
-      - [ ] Personal data identified and documented
-      - [ ] Legal basis for processing defined
-      - [ ] Data minimization principle applied
-      
-      **User Rights**
-      - [ ] Right to access implemented
-      - [ ] Right to rectification supported
-      - [ ] Right to erasure (RTBF) supported
-      - [ ] Data portability considered
-      
-      **Security & Governance**
-      - [ ] Data retention period defined
-      - [ ] Third-party processors identified
-      - [ ] Privacy by design applied
-      - [ ] DPIA required? (if high risk)
-    inputs:
-      spec: "functional_spec"
-    outputs:
-      - rgpd_report
-      - rgpd_status
-
   - id: security-review
-    name: "2.2 🔒 Security Review"
+    name: "2.1 🔒 Security Review"
     action: review
     agent: GovAgent
     description: |
-      Security assessment checklist:
+      Security assessment based on the specification:
       
       **Authentication & Authorization**
       - [ ] Auth mechanism defined
@@ -107,238 +61,109 @@ steps:
       - [ ] Session management
       
       **Data Protection**
-      - [ ] Encryption at rest
-      - [ ] Encryption in transit (TLS)
+      - [ ] Encryption requirements
       - [ ] Sensitive data handling
       
       **Input/Output Security**
       - [ ] Input validation strategy
       - [ ] Output encoding
-      - [ ] SQL injection prevention
-      - [ ] XSS prevention
-      - [ ] CSRF protection
+      - [ ] Injection prevention
       
-      **Infrastructure**
-      - [ ] Secrets management
-      - [ ] Logging (without PII)
-      - [ ] Rate limiting
-      - [ ] DDoS considerations
+      Identify any security concerns and recommendations.
     inputs:
-      spec: "functional_spec"
+      spec: "spec_document"
     outputs:
       - security_report
-      - security_status
 
-  - id: architecture-review
-    name: "2.3 🏗️ Architecture Review"
-    action: review
-    agent: GovAgent
-    description: |
-      Architecture validation:
-      
-      **Consistency**
-      - [ ] Aligns with existing architecture
-      - [ ] Follows established patterns
-      - [ ] Uses approved technologies
-      
-      **Quality Attributes**
-      - [ ] Scalability addressed
-      - [ ] Performance requirements met
-      - [ ] Reliability/Availability design
-      - [ ] Maintainability considered
-      
-      **Technical Debt**
-      - [ ] No unnecessary complexity
-      - [ ] Reuses existing components
-      - [ ] Technical debt acceptable
-      
-      **Integration**
-      - [ ] API contracts defined
-      - [ ] Event/message schemas
-      - [ ] Database changes documented
-    inputs:
-      spec: "functional_spec"
-    outputs:
-      - architecture_report
-      - architecture_status
-
-  - id: design-review
-    name: "2.4 🎨 Design System Review"
+  - id: rgpd-review
+    name: "2.2 🛡️ RGPD Review"
     action: review
     agent: GovAgent
     description: |
-      Design System compliance (if UI involved):
+      GDPR/RGPD compliance check:
       
-      **Components**
-      - [ ] Uses Design System components
-      - [ ] No unauthorized custom components
-      - [ ] Proper component composition
-      
-      **Visual Consistency**
-      - [ ] Color tokens used correctly
-      - [ ] Typography follows guidelines
-      - [ ] Spacing uses standard scale
-      - [ ] Icons from approved library
-      
-      **Accessibility (WCAG 2.1 AA)**
-      - [ ] Color contrast ratios
-      - [ ] Keyboard navigation
-      - [ ] Screen reader support
-      - [ ] Focus indicators
+      **Data Collection**
+      - [ ] Personal data identified
+      - [ ] Legal basis for processing
+      - [ ] Data minimization applied
       
-      **Responsive Design**
-      - [ ] Mobile breakpoints defined
-      - [ ] Touch targets adequate
-      - [ ] Dark mode support (if applicable)
+      **User Rights**
+      - [ ] Right to access
+      - [ ] Right to rectification
+      - [ ] Right to erasure
+      
+      **Governance**
+      - [ ] Data retention period
+      - [ ] Third-party processors
+      - [ ] Privacy by design
     inputs:
-      spec: "functional_spec"
+      spec: "spec_document"
     outputs:
-      - design_report
-      - design_status
+      - rgpd_report
 
   # ═══════════════════════════════════════════════════════════════
-  # PHASE 3: TECHNICAL PLANNING
+  # PHASE 3: PLANNING
   # ═══════════════════════════════════════════════════════════════
 
-  - id: technical-plan
-    name: "3.1 Technical Planning"
+  - id: create-plan
+    name: "3. Create Implementation Plan"
     action: call_agent
     agent: PlanAgent
     description: |
-      Create detailed technical plan:
+      Create a detailed implementation plan incorporating validation feedback.
       
-      **Architecture Decisions**
+      Include:
+      - Technical approach
       - Components to create/modify
-      - Database schema changes
-      - API endpoints
-      - Integration points
-      
-      **Task Breakdown**
-      - Granular tasks (1-3 days each)
-      - Clear acceptance criteria
-      - Dependencies mapped
-      - Effort estimates (S/M/L/XL)
-      
-      **Risk Mitigation**
-      - Technical risks identified
-      - Mitigation strategies
-      - Spike tasks if needed
-    inputs:
-      spec: "functional_spec"
-      reviews: ["rgpd_report", "security_report", "architecture_report"]
-    outputs:
-      - technical_plan
-      - task_list
-
-  - id: test-strategy
-    name: "3.2 🧪 Test Strategy"
-    action: call_agent
-    agent: TestAgent
-    description: |
-      Define comprehensive test strategy:
-      
-      **Unit Tests**
-      - Critical business logic
-      - Edge cases
-      - Error handling
-      - Target: >80% coverage
-      
-      **Integration Tests**
-      - API contracts
-      - Database operations
-      - External service mocks
-      
-      **E2E Tests**
-      - Critical user journeys
-      - Happy path scenarios
-      - Key error scenarios
-      
-      **Non-Functional Tests**
-      - Performance benchmarks
-      - Load testing thresholds
-      - Security scan requirements
+      - Security measures to implement
+      - RGPD compliance measures
+      - Dependencies and order
+      - Risk assessment
     inputs:
-      spec: "functional_spec"
-      plan: "technical_plan"
+      spec: "spec_document"
+      reviews: ["security_report", "rgpd_report"]
     outputs:
-      - test_strategy
-      - test_cases
+      - plan_document
 
   # ═══════════════════════════════════════════════════════════════
-  # PHASE 4: DOCUMENTATION & FINALIZATION
+  # PHASE 4: TASKS
   # ═══════════════════════════════════════════════════════════════
 
-  - id: documentation
-    name: "4.1 📚 Documentation Plan"
-    action: generate_content
+  - id: generate-tasks
+    name: "4. Generate Tasks"
+    action: call_agent
+    agent: PlanAgent
     description: |
-      Identify documentation needs:
-      
-      **User Documentation**
-      - [ ] User guide updates
-      - [ ] FAQ additions
-      - [ ] Tutorial/walkthrough
+      Break down the plan into atomic tasks.
       
-      **Technical Documentation**
-      - [ ] API documentation
-      - [ ] Architecture Decision Record (ADR)
-      - [ ] Runbook updates
-      - [ ] README updates
-      
-      **Release Documentation**
-      - [ ] Changelog entry
-      - [ ] Release notes
-      - [ ] Migration guide (if breaking changes)
+      Each task should:
+      - Be completable in 1-2 hours
+      - Have clear acceptance criteria
+      - Include security/RGPD considerations
+      - Be independently testable
     inputs:
-      spec: "functional_spec"
-      plan: "technical_plan"
+      source: "plan_document"
     outputs:
-      - documentation_plan
+      - tasks_document
 
-  - id: final-approval
-    name: "4.2 ✅ Final Approval Gate"
-    action: review
-    agent: GovAgent
-    description: |
-      Final checklist before development starts:
-      
-      **Specification**
-      - [ ] Functional spec complete and approved
-      - [ ] All [TO FILL] sections resolved
-      - [ ] Stakeholder sign-off obtained
-      
-      **Compliance**
-      - [ ] RGPD review: PASSED
-      - [ ] Security review: PASSED
-      - [ ] Architecture review: PASSED
-      - [ ] Design review: PASSED (if applicable)
-      
-      **Planning**
-      - [ ] Technical plan approved
-      - [ ] Tasks created in ADO
-      - [ ] Test strategy defined
-      - [ ] Documentation plan ready
-      
-      **Ready for Development** ✅
-    inputs:
-      all_artifacts: true
-    outputs:
-      - final_approval
-      - development_ready
+  # ═══════════════════════════════════════════════════════════════
+  # PHASE 5: IMPLEMENTATION
+  # ═══════════════════════════════════════════════════════════════
 
-  - id: create-tasks
-    name: "4.3 Create ADO Work Items"
-    action: create_file
+  - id: implement
+    name: "5. Implement"
+    action: call_agent
+    agent: SpecAgent
     description: |
-      Generate Azure DevOps work items:
-      - Create Tasks from technical plan
-      - Link to parent Feature
-      - Set estimates and priorities
-      - Assign to sprint
-      
-      Output format ready for ADO import or manual creation.
+      Implement the tasks following security and RGPD guidelines.
+      
+      For each task:
+      - Implement following project conventions
+      - Apply security measures
+      - Ensure RGPD compliance
+      - Write appropriate tests
+      - Update task status when complete
     inputs:
-      tasks: "task_list"
-      feature_id: "context_id"
+      source: "tasks_document"
     outputs:
-      - ado_work_items
+      - implementation

package/starter-kit/workflows/feature-standard.yaml

@@ -1,92 +1,96 @@
 # Feature Standard Workflow
-# Used for creating functional specifications from Azure DevOps Feature work items
+# Standard workflow: spec → plan → tasks → implement
 
 name: feature-standard
-displayName: "Feature Specification"
-description: "Creates a complete functional specification document from an Azure DevOps Feature work item"
+displayName: "Standard Feature"
+description: "Standard feature workflow: specification → plan → tasks → implementation"
 
 metadata:
-  version: "1.0"
+  version: "2.0"
   author: "Spec-Kit"
   tags:
     - feature
     - specification
-    - functional
+    - standard
 
 template: functional-spec.md
 defaultAgent: SpecAgent
 
 steps:
-  - id: fetch-workitem
-    name: "Fetch Azure DevOps Work Item"
-    action: fetch_ado
-    description: |
-      Retrieve the Feature work item from Azure DevOps.
-      Extract: Title, Description, Acceptance Criteria, Tags, Links, and Parent/Child relationships.
-    outputs:
-      - workitem_data
-      - linked_items
-
-  - id: analyze-requirements
-    name: "Analyze Requirements"
+  # Step 1: Create Specification
+  - id: create-spec
+    name: "1. Create Specification"
     action: call_agent
     agent: SpecAgent
     description: |
-      Analyze the work item data to identify:
-      - Core functional requirements
-      - Non-functional requirements (performance, security, etc.)
-      - User personas and use cases
+      Create a functional specification based on user requirements.
+      
+      Include:
+      - Feature summary and objectives
+      - User stories with acceptance criteria
+      - Functional requirements
+      - Non-functional requirements (if applicable)
       - Dependencies and constraints
-      - Risks and assumptions
+      
+      Mark unclear sections with [NEEDS CLARIFICATION] for review.
     inputs:
-      source: "workitem_data"
+      - name: requirements
+        description: "Feature description from user"
+        required: true
     outputs:
-      - requirements_analysis
+      - spec_document
 
-  - id: generate-spec
-    name: "Generate Specification Document"
-    action: generate_content
-    agent: SpecAgent
+  # Step 2: Create Implementation Plan
+  - id: create-plan
+    name: "2. Create Implementation Plan"
+    action: call_agent
+    agent: PlanAgent
     description: |
-      Using the template and analyzed requirements, generate the functional specification.
+      Create a detailed implementation plan based on the specification.
       
-      Guidelines:
-      - Fill all sections with available data
-      - Mark unclear sections with [TO FILL] for human review
-      - Include traceability links to Azure DevOps
-      - Follow the template structure strictly
+      Include:
+      - Technical approach
+      - Components to create/modify
+      - Dependencies and order
+      - Risk assessment
+      - Estimated effort
     inputs:
-      template: "functional-spec.md"
-      data: "requirements_analysis"
+      source: "spec_document"
     outputs:
-      - spec_document
+      - plan_document
 
-  - id: review-spec
-    name: "Review & Validate"
-    action: review
-    agent: GovAgent
+  # Step 3: Generate Task Breakdown
+  - id: generate-tasks
+    name: "3. Generate Tasks"
+    action: call_agent
+    agent: PlanAgent
     description: |
-      Review the generated specification for:
-      - Completeness (all required sections filled)
-      - Consistency (no contradictions)
-      - Clarity (understandable by all stakeholders)
-      - Traceability (links to source requirements)
+      Break down the plan into atomic, actionable tasks.
       
-      Suggest improvements if needed.
+      Each task should:
+      - Be completable in 1-2 hours
+      - Have clear acceptance criteria
+      - Be independent when possible
+      - Include file paths if known
     inputs:
-      document: "spec_document"
+      source: "plan_document"
     outputs:
-      - review_feedback
-      - validated_spec
+      - tasks_document
 
-  - id: create-file
-    name: "Save Specification"
-    action: create_file
+  # Step 4: Implement
+  - id: implement
+    name: "4. Implement"
+    action: call_agent
+    agent: SpecAgent
     description: |
-      Save the validated specification as a Markdown file.
-      Suggested location: `specs/{workitem_id}-functional-spec.md`
+      Implement the tasks one by one.
+      
+      For each task:
+      - Read the task description
+      - Implement following project conventions
+      - Update task status when complete
+      - Proceed to next task
     inputs:
-      content: "validated_spec"
-      filename_pattern: "{context_id}-functional-spec.md"
+      source: "tasks_document"
     outputs:
-      - file_path
+      - implementation