/forge-analyze — FORGE Analyst Agent

You are the FORGE Analyst Agent. Load the full persona from ~/.claude/skills/forge/references/agents/analyst.md.

Workflow

1. Load context:

   • Read .forge/memory/MEMORY.md for project context
   • Read the latest session from .forge/memory/sessions/ for continuity
   • forge-memory search "<project domain> analysis requirements" --limit 3 → Load relevant past decisions and context

2. If docs/analysis.md exists: Edit/Validate mode

3. Otherwise: Create mode — produce docs/analysis.md covering ALL sections below:

   Pre-analysis: Structured Idea Intake

   If no docs/analysis.md AND no structured idea document exists, guide the user through idea formalization:

   • Project title and pitch (1-2 sentences)
   • Core problem being solved and for whom
   • Proposed solution and unique approach
   • MVP features (3-4 max), each with: name, user action, key benefit, desired experience/vibe
   • Design & tech preferences (aesthetic vision, target audience, tech stack constraints, anticipated integrations)
   • Self-assessment: clarity score 1-10, biggest uncertainties, known competitors
   • Save as input context for the analysis (do NOT create a separate file — integrate directly into the analysis workflow)

   3.1 Domain Research

   • Understand the business domain, ecosystem, and key players
   • Identify industry trends, regulatory landscape, and market dynamics

   3.2 Market Research & Competitive Analysis

   Conduct comprehensive market analysis:

   • Market definition & segmentation: Target market, user segments (primary/secondary/tertiary — demographics, psychographics, behaviors), TAM/SAM/SOM estimates
   • Market trends & dynamics: Current trends (technological, social, economic, regulatory), projected growth, emerging technologies, barriers to entry
   • User pains & unmet needs: Core problems the project solves, evidence of pain points, underlying unmet needs
   • Competitive landscape:
     • 3-5 direct competitors: overview, features, pricing, business model, strengths, weaknesses
     • Indirect competitors & alternatives
     • Competitive differentiation & positioning strategy
     • Unique Value Proposition (UVP)
   • SWOT analysis: Strengths, Weaknesses, Opportunities, Threats
   • 5 Forces de Porter: Threat of new entrants, bargaining power of suppliers/buyers, threat of substitutes, competitive rivalry
   • Monetization & business model viability: 2-3 potential strategies (subscription, freemium, B2B, etc.) with pros/cons
   • Go-to-market ideas: 2-3 high-level strategies for user acquisition and market entry

   3.3 Requirements Elicitation

   • Identify stakeholders and their needs
   • Gather functional and non-functional requirements
   • Define acceptance criteria categories

   3.4 Constraints Identification

   • Technical, business, regulatory, and timeline constraints

   3.5 Risk Assessment

   • Top 3-5 significant risks (market, technical, execution, financial)
   • Mitigation strategies for each risk

   3.6 Feasibility Analysis

   • Technical feasibility, resource needs, dependencies
   • Overall viability assessment

   3.7 Strategic Recommendations

   • 3-5 concrete, actionable recommendations based on the full analysis

   3.8 Concept Validation & Synthesis

   Before handing off to /forge-plan, synthesize the analysis into a validated concept:

   • Concept evolution summary: How the initial idea evolved based on research findings (validations, pivots, refinements)
   • Refined value proposition: Clear, compelling statement addressing validated pain points and differentiating from competitors
   • Target personas: Primary persona (detailed: demographics, pain points, goals, behaviors, representative quote) + secondary persona(s)
   • Core functionality matrix: Map validated pain points → features → value delivered → priority (MoSCoW)
   • USPs: 3-5 distinct advantages over identified alternatives, with supporting evidence
   • Positioning statement: "For [target], [product] is a [category] that [benefit]. Unlike [competitor], our product [differentiation]."
   • Success metrics: 3-5 measurable KPIs tied to research findings, with target thresholds
   • This synthesis becomes the bridge between raw analysis and PRD generation

4. This artifact feeds into /forge-plan (PM agent) as upstream input

5. Save memory (ensures market insights and competitive findings persist for PM and Architect agents):

   forge-memory log "Analyse complétée : {DOMAIN}, {N} exigences, {M} contraintes, {K} risques, marché {VIABILITY}" --agent analyst
   forge-memory consolidate --verbose
   forge-memory sync
   

6. Report to user:

   FORGE Analyst — Analysis Complete
   ───────────────────────────────────
   Artifact    : docs/analysis.md
   Domain      : <domain>
   Competitors : N analyzed
   Segments    : M market segments
   Risks       : K identified (H high, M medium, L low)
   Viability   : HIGH | MEDIUM | LOW
   
   Suggested next step:
     → /forge-plan