feat: Add new Discovery Phase for PM and pass product staretgy and pain points etc as context to requirement analysis

README.md

@@ -10,7 +10,7 @@ AI-DLC is an intelligent software development workflow that adapts to your needs
 - [Quick Start](#quick-start)
 - [Platform-Specific Setup](#platform-specific-setup)
 - [Usage](#usage)
-- [Three-Phase Adaptive Workflow](#three-phase-adaptive-workflow)
+- [Four-Phase Adaptive Workflow](#four-phase-adaptive-workflow)
 - [Key Features](#key-features)
 - [Extensions](#extensions)
 - [Tenets](#tenets)
@@ -227,6 +227,7 @@ xcopy "%USERPROFILE%\Downloads\aidlc-rules\aws-aidlc-rule-details" ".aidlc-rule-
 │       └── ai-dlc-workflow.mdc
 └── .aidlc-rule-details/
     ├── common/
+    ├── discovery/
     ├── inception/
     ├── construction/
     └── operations/
@@ -303,6 +304,7 @@ xcopy "%USERPROFILE%\Downloads\aidlc-rules\aws-aidlc-rule-details" ".aidlc-rule-
 │   └── core-workflow.md
 └── .aidlc-rule-details/
     ├── common/
+    ├── discovery/
     ├── inception/
     ├── construction/
     └── operations/
@@ -376,6 +378,7 @@ xcopy "%USERPROFILE%\Downloads\aidlc-rules\aws-aidlc-rule-details" ".aidlc-rule-
 ├── CLAUDE.md
 └── .aidlc-rule-details/
     ├── common/
+    ├── discovery/
     ├── inception/
     ├── construction/
     └── operations/
@@ -426,6 +429,7 @@ xcopy "%USERPROFILE%\Downloads\aidlc-rules\aws-aidlc-rule-details" ".aidlc-rule-
 │   └── copilot-instructions.md
 └── .aidlc-rule-details/
     ├── common/
+    ├── discovery/
     ├── inception/
     ├── construction/
     └── operations/
@@ -456,13 +460,20 @@ If your agent has no convention for rules files, place both folders at your proj
 
 ---
 
-## Three-Phase Adaptive Workflow
+## Four-Phase Adaptive Workflow
 
-AI-DLC follows a structured three-phase approach that adapts to your project's complexity:
+AI-DLC follows a structured four-phase approach that adapts to your project's complexity:
+
+### � DISCOVERY PHASE (PM-Led, Greenfield Only)
+Defines **WHO** the customer is, **WHAT** problem to solve, and **WHY** it matters
+- Envision: Gather customer pain points and create PRFAQ using Working Backwards method
+- Product Strategy: Positioning, differentiation, and business model decisions
+- Go-to-Market: Marketing, sales, and launch planning
+- All three stages produce a single living document that Inception consumes
 
 ### 🔵 INCEPTION PHASE
 Determines **WHAT** to build and **WHY**
-- Requirements analysis and validation
+- Requirements analysis and validation (informed by Discovery Document for Greenfield)
 - User story creation (when applicable)
 - Application Design and creating units of work for parallel development
 - Risk assessment and complexity evaluation
@@ -533,6 +544,10 @@ The workflow currently ships with a baseline security extension.
 
 ```
 aws-aidlc-rule-details/
+├── discovery/                         # Discovery phase rules (Greenfield)
+│   ├── envision.md
+│   ├── product-strategy.md
+│   └── go-to-market.md
 └── extensions/
     └── security/                      # Extension category
         └── baseline/

aidlc-rules/aws-aidlc-rule-details/common/process-overview.md

@@ -7,17 +7,19 @@
 - **core-workflow.md**: User-facing welcome message with ASCII diagram
 - **README.md**: Human-readable documentation for repository
 
-## The Three-Phase Lifecycle:
+## The Four-Phase Lifecycle:
+• **DISCOVERY PHASE**: PM-led product definition (Envision + Product Strategy + Go-to-Market) — Greenfield only
 • **INCEPTION PHASE**: Planning and architecture (Workspace Detection + conditional phases + Workflow Planning)
 • **CONSTRUCTION PHASE**: Design, implementation, build and test (per-unit design + Code Planning/Generation + Build & Test)
 • **OPERATIONS PHASE**: Placeholder for future deployment and monitoring workflows
 
 ## The Adaptive Workflow:
-• **Workspace Detection** (always) → **Reverse Engineering** (brownfield only) → **Requirements Analysis** (always, adaptive depth) → **Conditional Phases** (as needed) → **Workflow Planning** (always) → **Code Generation** (always, per-unit) → **Build and Test** (always)
+• **Workspace Detection** (always) → **DISCOVERY PHASE** (greenfield only: Envision → Product Strategy → Go-to-Market) → **Reverse Engineering** (brownfield only) → **Requirements Analysis** (always, adaptive depth) → **Conditional Phases** (as needed) → **Workflow Planning** (always) → **Code Generation** (always, per-unit) → **Build and Test** (always)
 
 ## How It Works:
 • **AI analyzes** your request, workspace, and complexity to determine which stages are needed
 • **These stages always execute**: Workspace Detection, Requirements Analysis (adaptive depth), Workflow Planning, Code Generation (per-unit), Build and Test
+• **Discovery Phase executes for Greenfield projects**: Envision, Product Strategy, Go-to-Market — producing a living document that Inception consumes
 • **All other stages are conditional**: Reverse Engineering, User Stories, Application Design, Units Generation, per-unit design stages (Functional Design, NFR Requirements, NFR Design, Infrastructure Design)
 • **No fixed sequences**: Stages execute in the order that makes sense for your specific task
 
@@ -28,12 +30,18 @@
 • **Collectively decide** on architectural approach when needed
 • **Important**: This is a team effort - involve relevant stakeholders for each phase
 
-## AI-DLC Three-Phase Workflow:
+## AI-DLC Four-Phase Workflow:
 
 ```mermaid
 flowchart TD
     Start(["User Request"])
 
+    subgraph DISCOVERY["🟣 DISCOVERY PHASE (PM-Led, Greenfield Only)"]
+        ENV["Envision<br/><b>CONDITIONAL</b>"]
+        PS["Product Strategy<br/><b>CONDITIONAL</b>"]
+        GTM["Go-to-Market<br/><b>CONDITIONAL</b>"]
+    end
+
     subgraph INCEPTION["🔵 INCEPTION PHASE"]
         WD["Workspace Detection<br/><b>ALWAYS</b>"]
         RE["Reverse Engineering<br/><b>CONDITIONAL</b>"]
@@ -58,6 +66,10 @@ flowchart TD
     end
 
     Start --> WD
+    WD -.-> ENV
+    ENV --> PS
+    PS --> GTM
+    GTM --> RA
     WD -.-> RE
     WD --> RA
     RE --> RA
@@ -87,19 +99,21 @@ flowchart TD
     style WD fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
     style RA fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
     style WP fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
-
     style CG fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
     style BT fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
     style OPS fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
+    style ENV fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,stroke-dasharray: 5 5,color:#000
+    style PS fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,stroke-dasharray: 5 5,color:#000
+    style GTM fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,stroke-dasharray: 5 5,color:#000
     style RE fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
     style Stories fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
     style AppDesign fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
-
     style UnitsG fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
     style FD fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
     style NFRA fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
     style NFRD fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
     style ID fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
+    style DISCOVERY fill:#E1BEE7,stroke:#6A1B9A,stroke-width:3px, color:#000
     style INCEPTION fill:#BBDEFB,stroke:#1565C0,stroke-width:3px, color:#000
     style CONSTRUCTION fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px, color:#000
     style OPERATIONS fill:#FFF59D,stroke:#F57F17,stroke-width:3px, color:#000
@@ -111,6 +125,11 @@ flowchart TD
 
 **Stage Descriptions:**
 
+**🟣 DISCOVERY PHASE** - PM-Led Product Definition (Greenfield Only)
+- Envision: Gather customer pain points, synthesize into categorized analysis, generate PRFAQ using Working Backwards method with intelligent defaults (CONDITIONAL - Greenfield only)
+- Product Strategy: Capture positioning, differentiation, business model decisions informed by validated pain points and PRFAQ (CONDITIONAL - Greenfield only)
+- Go-to-Market: Marketing strategy, sales approach, launch planning before Construction begins (CONDITIONAL - Greenfield only)
+
 **🔵 INCEPTION PHASE** - Planning and Architecture
 - Workspace Detection: Analyze workspace state and project type (ALWAYS)
 - Reverse Engineering: Analyze existing codebase (CONDITIONAL - Brownfield only)
@@ -134,6 +153,7 @@ flowchart TD
 **Key Principles:**
 - Phases execute only when they add value
 - Each phase independently evaluated
+- DISCOVERY focuses on "who" and "what problem" (PM-led, Greenfield only)
 - INCEPTION focuses on "what" and "why"
 - CONSTRUCTION focuses on "how" plus "build and test"
 - OPERATIONS is placeholder for future expansion

aidlc-rules/aws-aidlc-rule-details/common/welcome-message.md

@@ -18,13 +18,23 @@ AI-DLC is a structured yet flexible software development process that adapts to
 - **Documents everything** so you have a complete record of decisions and rationale
 - **Guides you through each phase** with clear checkpoints and approval gates
 
-## The Three-Phase Lifecycle
+## The Four-Phase Lifecycle
 
 ```
                          User Request
                               |
                               v
         ╔═══════════════════════════════════════╗
+        ║     DISCOVERY PHASE (PM-Led)          ║
+        ║     COND - Greenfield Only            ║
+        ╠═══════════════════════════════════════╣
+        ║ • Envision (pain points + PRFAQ)      ║
+        ║ • Product Strategy                    ║
+        ║ • Go-to-Market                        ║
+        ╚═══════════════════════════════════════╝
+                              |
+                              v
+        ╔═══════════════════════════════════════╗
         ║     INCEPTION PHASE                   ║
         ║     Planning & Application Design     ║
         ╠═══════════════════════════════════════╣
@@ -65,9 +75,15 @@ AI-DLC is a structured yet flexible software development process that adapts to
 
 ### Phase Breakdown:
 
+**DISCOVERY PHASE** - *PM-Led Product Definition (Greenfield Only)*
+- **Purpose**: Defines WHO the customer is, WHAT problem to solve, and WHY it matters — before any technical work begins
+- **Activities**: Gathering customer pain points (interactive, URL analysis, or hybrid), creating PRFAQ using Working Backwards, defining product strategy, planning go-to-market
+- **Output**: A single living Discovery Document containing validated PRFAQ, product strategy, and go-to-market plan
+- **Your Role**: Lead the product vision, answer questions (with intelligent defaults to confirm or override), review and approve each stage
+
 **INCEPTION PHASE** - *Planning & Application Design*
 - **Purpose**: Determines WHAT to build and WHY
-- **Activities**: Understanding requirements, analyzing existing code (if any), planning the approach
+- **Activities**: Understanding requirements (informed by Discovery Document for Greenfield), analyzing existing code (if any), planning the approach
 - **Output**: Clear requirements, execution plan, decisions on the number of units of work for parallel development
 - **Your Role**: Answer questions, review plans, approve direction
 
@@ -94,11 +110,12 @@ AI-DLC is a structured yet flexible software development process that adapts to
 ## What Happens Next:
 
 1. **I'll analyze your workspace** to understand if this is a new or existing project
-2. **I'll gather requirements** and ask clarifying questions if needed
-3. **I'll create an execution plan** showing which stages I propose to run and why
-4. **You'll review and approve** the plan (or request changes)
-5. **We'll execute the plan** with checkpoints at each major stage
-6. **You'll get working code** with complete documentation and tests
+2. **For new projects (Greenfield)**: I'll guide you through Discovery — gathering pain points, creating a PRFAQ, defining product strategy, and planning go-to-market
+3. **I'll gather requirements** and ask clarifying questions if needed (informed by Discovery for Greenfield)
+4. **I'll create an execution plan** showing which stages I propose to run and why
+5. **You'll review and approve** the plan (or request changes)
+6. **We'll execute the plan** with checkpoints at each major stage
+7. **You'll get working code** with complete documentation and tests
 
 The AI-DLC process adapts to:
 - 📋 Your intent clarity and complexity