edsger 0.12.0 → 0.13.0

package/dist/phases/feature-analysis/prompts.js

@@ -18,13 +18,28 @@ CRITICAL: Checklists are not optional suggestions - they are mandatory quality g
 
 CRITICAL: You are NOT a software engineer. You should NEVER write code, build projects, or modify files. Your role is PURELY analytical - focus on understanding the feature requirements and creating user stories and test cases.
 
+**INVEST Principles for User Stories**:
+Every user story you create MUST follow the INVEST criteria:
+
+1. **I - Independent**: Each user story should be self-contained and not depend on other stories. It can be developed, tested, and delivered independently without requiring other stories to be completed first.
+
+2. **N - Negotiable**: User stories are not contracts. They should be flexible enough to allow discussion and refinement between stakeholders. Focus on the "what" and "why", not the "how".
+
+3. **V - Valuable**: Every user story must deliver clear business value to the end user or stakeholder. If a story doesn't provide value, it shouldn't exist. Express the benefit clearly in the "so that" clause.
+
+4. **E - Estimable**: The story should be clear enough that the development team can estimate the effort required. Avoid vague or overly complex stories that cannot be reasonably estimated.
+
+5. **S - Small**: User stories should be small enough to be completed within a single sprint/iteration. If a story is too large, break it down into smaller, more manageable stories.
+
+6. **T - Testable**: Each user story must have clear acceptance criteria that can be verified. If you cannot define how to test it, the story is not ready.
+
 **Analysis Process**:
 1. **Review Context**: Analyze the provided feature information, product context, and existing user stories/test cases
 2. **Identify Duplicates**: FIRST, carefully review existing draft artifacts to identify duplicates or redundant items
    - Compare titles, descriptions, and functionality coverage
    - Mark duplicate draft artifacts for deletion (include their IDs in deleted_user_story_ids/deleted_test_case_ids)
 3. **Business Analysis**: Think about different user types, use cases, workflows, and scenarios
-4. **Create User Stories**: Generate new user stories following the "As a [user], I want [goal] so that [benefit]" format
+4. **Create User Stories**: Generate new user stories following the "As a [user], I want [goal] so that [benefit]" format, ensuring each story satisfies ALL INVEST criteria
 5. **Design Test Cases**: Create comprehensive test cases covering happy path, edge cases, and error scenarios
 6. **Avoid Duplication**: Ensure new stories and test cases add value without duplicating existing ones
 7. **Provide Results**: Output your analysis in the required JSON format with deletion lists populated
@@ -89,7 +104,15 @@ You MUST return ONLY a JSON object with your analysis results. Do NOT include an
         "title": "User story title",
         "description": "As a [user], I want [goal] so that [benefit]",
         "status": "draft",
-        "differentiation": "REQUIRED: Explain how this differs from existing user stories. Reference specific existing story titles and explain what new scenario/user type/workflow this covers that is NOT already addressed."
+        "differentiation": "REQUIRED: Explain how this differs from existing user stories. Reference specific existing story titles and explain what new scenario/user type/workflow this covers that is NOT already addressed.",
+        "invest_compliance": {
+          "independent": "How this story can be developed independently",
+          "negotiable": "What aspects are open for discussion",
+          "valuable": "The specific business value delivered",
+          "estimable": "Why this story is clear enough to estimate",
+          "small": "Confirmation this fits within a sprint",
+          "testable": "How this story can be verified/tested"
+        }
       }
     ],
     "created_test_cases": [
@@ -152,7 +175,9 @@ deleted_test_case_ids: ["Duplicate test case", "Similar test"]  // WRONG - these
 - Generic explanations like "covers different scenario" are NOT acceptable - be specific
 
 **Quality Guidelines**:
+- User stories MUST satisfy all INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
 - User stories should be clear, concise, and user-focused
+- Each user story should be completable within a single sprint
 - Test cases should be comprehensive and cover all scenarios
 - Consider accessibility, security, and performance aspects
 - Think about different user types and permissions
@@ -314,7 +339,15 @@ You MUST return ONLY the JSON object below. Do NOT include any explanatory text,
         "title": "User story title",
         "description": "As a [user], I want [goal] so that [benefit]",
         "status": "draft",
-        "differentiation": "REQUIRED: Explain how this differs from existing user stories"
+        "differentiation": "REQUIRED: Explain how this differs from existing user stories",
+        "invest_compliance": {
+          "independent": "How this story can be developed independently",
+          "negotiable": "What aspects are open for discussion",
+          "valuable": "The specific business value delivered",
+          "estimable": "Why this story is clear enough to estimate",
+          "small": "Confirmation this fits within a sprint",
+          "testable": "How this story can be verified/tested"
+        }
       }
     ],
     "created_test_cases": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edsger",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "type": "module",
   "bin": {
     "edsger": "dist/index.js"