analyze-projectlisted

# SPARK Analysis Conduct SPARK methodology analysis for new project inception. ## When to Use - At the very beginning of a new project - When evaluating a significant new feature or system - Before running `bootstrap-project` to validate project viability - When pivoting or reassessing an existing project ## What is SPARK? SPARK is a structured inception methodology for validating project viability: - **S**takeholders: Who is affected and who has influence? - **P**roblem: What problem are we solving? What's the scope? - **A**nalysis: What exists? What are the options? What are the constraints? - **R**isks: What could go wrong? How do we mitigate? - **K**nowledge: What do we know? What gaps exist? > **Alternative Interpretation**: Some practitioners use SPARK as: **S**ituation, **P**roposal, **A**greement, **R**esources, **K**ickers. This variant focuses more on proposal-driven inception where the situation is assessed, a proposal is made, agreement is sought, resources are identified, and potential "kickers" (deal-breakers or critical success factors) are surfaced early. Choose the interpretation that best fits your project context. ## Required Inputs 1. **Project idea/concept** (initial description) 2. **Context** (why now? what triggered this?) 3. **Initial stakeholder list** (who asked for this?) 4. **Time constraints** (deadline pressures?) 5. **Budget/resource constraints** (if known) ## Workflow ### Phase 1: Stakeholder Analysis Identify and analyze all stak