openclaw-node-harness 2.0.0

package/skills/proto-persona/examples/sample.md

@@ -0,0 +1,97 @@
+# Proto-Persona Examples
+
+## Example 1: "Manager Mike" (Good Proto-Persona)
+
+```markdown
+### Name
+- Manager Mike
+
+### Bio & Demographics
+- 35-42 years old, lives in urban/suburban areas (Chicago, Seattle, Austin)
+- Director of Product at mid-sized B2B SaaS companies (100-500 employees)
+- Married with 2 kids, commutes 30 min by car, values work-life balance
+- Active on LinkedIn and ProductHunt, attends 1-2 PM conferences per year
+- Reads PM blogs/newsletters (Lenny's, Stratechery), listens to podcasts
+- Plays rec basketball on weekends
+
+### Quotes
+- "I spend more time in status meetings than actually building product."
+- "My CEO asks me for data I don't have, and it takes 3 days to get it from engineering."
+- "Every tool promises to save time, but they all require a week of onboarding."
+
+### Pains
+- Spends 10+ hours/week in status meetings and writing updates
+- No single source of truth for product metrics—data is scattered across tools
+- Pressure to ship faster, but team is stretched thin
+
+### What is This Person Trying to Accomplish?
+- Deliver roadmap milestones on time without burning out the team
+- Make data-driven prioritization decisions in real-time
+- Communicate progress to execs without manual reporting overhead
+
+### Goals
+- Be seen as a strategic thinker, not just a feature factory manager
+- Get promoted to VP of Product within 2 years
+- Spend more time with family (leave work by 6pm)
+
+### Attitudes & Influences
+- **Decision-Making Authority:** Can approve tools up to $15k/year; needs VP/CFO approval above that
+- **Decision Influencers:** Peer PMs in Slack communities, former colleagues, analyst reports (Gartner)
+- **Beliefs & Attitudes:**
+  - Skeptical of tools that require developer setup
+  - Values ease of use over feature depth
+  - Prefers tools that integrate with existing stack (Jira, Slack, Figma)
+  - Willing to pay more for great UX and support
+```
+
+**Why this works:**
+- Specific demographics tied to behavior (not just "35-42")
+- Quotes reveal real frustrations (not generic platitudes)
+- Pains are measurable and specific
+- Goals include professional and personal motivations
+- Decision-making context is clear
+
+---
+
+## Example 2: Bad Proto-Persona (Too Generic)
+
+```markdown
+### Name
+- John
+
+### Bio & Demographics
+- 30-50 years old
+- Lives somewhere
+- Works in tech
+
+### Quotes
+- "I want better tools."
+
+### Pains
+- Tools are bad
+
+### What is This Person Trying to Accomplish?
+- Use good software
+
+### Goals
+- Be productive
+
+### Attitudes & Influences
+- **Decision-Making Authority:** Maybe
+- **Decision Influencers:** People
+- **Beliefs & Attitudes:** Likes good things
+```
+
+**Why this fails:**
+- Age range is too broad (20-year span)
+- No behavioral context ("works in tech" = meaningless)
+- Quotes are generic ("better tools" = every persona ever)
+- Pains are vague ("tools are bad" = not actionable)
+- No specific goals or influences
+
+**How to fix it:**
+- Narrow demographics: "35-45, Director-level, B2B SaaS"
+- Add behavioral details: "Remote-first, active in PM communities"
+- Use real quotes: "I spend 5 hours/week chasing down status updates"
+- Specify pains: "No visibility into what engineering is building"
+- Define goals: "Get promoted to VP within 2 years"

package/skills/proto-persona/template.md

@@ -0,0 +1,45 @@
+# Proto-Persona Template
+
+Use this template to capture a hypothesis-driven persona profile.
+
+## Provenance
+Adapted from `prompts/proto-persona-profile.md` in the `https://github.com/deanpeters/product-manager-prompts` repo.
+
+## Template
+```markdown
+### Name
+- [Alliterative name]
+
+### Bio & Demographics
+- [Age range]
+- [Geographic location]
+- [Social status]
+- [Online presence]
+- [Leisure activities]
+- [Career status]
+
+### Quotes
+- "[Quote 1]"
+- "[Quote 2]"
+- "[Quote 3]"
+
+### Pains
+- [Pain point 1]
+- [Pain point 2]
+- [Pain point 3]
+
+### What is This Person Trying to Accomplish?
+- [Behavior or outcome 1]
+- [Behavior or outcome 2]
+- [Behavior or outcome 3]
+
+### Goals
+- [Goal 1]
+- [Goal 2]
+- [Goal 3]
+
+### Attitudes & Influences
+- **Decision-Making Authority:** [Yes/No + context]
+- **Decision Influencers:** [Who influences this person]
+- **Beliefs & Attitudes:** [Beliefs/attitudes that impact decisions]
+```

package/skills/recommendation-canvas/SKILL.md

@@ -0,0 +1,382 @@
+---
+name: recommendation-canvas
+description: "Use this to build a structured recommendation canvas for AI product proposals, covering business outcomes, customer outcomes, problem framing, solution hypotheses, positioning, risks, and value justification."
+type: component
+triggers:
+  - "create a recommendation canvas"
+  - "build a product recommendation for stakeholders"
+  - "help me propose an AI solution with a canvas"
+  - "I need to pitch an AI feature to execs"
+negative_triggers:
+  - "write a PRD"
+  - "create a business case spreadsheet"
+  - "build a feature spec"
+---
+
+
+## Purpose
+Evaluate and propose AI product solutions using a structured canvas that assesses business outcomes, customer outcomes, problem framing, solution hypotheses, positioning, risks, and value justification. Use this to build a comprehensive, defensible recommendation for stakeholders and decision-makers—especially when proposing AI-powered features or products that carry higher uncertainty and risk.
+
+This is not a feature spec—it's a strategic proposal that articulates *why* this AI solution is worth building, *what* assumptions need validating, and *how* you'll measure success.
+
+## Key Concepts
+
+### The Recommendation Canvas Framework
+Created for Dean Peters' Productside "AI Innovation for Product Managers" class, the canvas synthesizes multiple PM frameworks into one strategic view:
+
+**Core Components:**
+1. **Business Outcome:** What's in it for the business?
+2. **Product Outcome:** What's in it for the customer?
+3. **Problem Statement:** Persona-centric problem framing
+4. **Solution Hypothesis:** If/then hypothesis with experiments
+5. **Positioning Statement:** Value prop and differentiation
+6. **Assumptions & Unknowns:** What could invalidate this?
+7. **PESTEL Risks:** Political, Economic, Social, Technological, Environmental, Legal
+8. **Value Justification:** Why this is worth doing
+9. **Success Metrics:** SMART metrics to measure impact
+10. **What's Next:** Strategic next steps
+
+### Why This Works
+- **Outcome-driven:** Forces clarity on business AND customer value
+- **Hypothesis-centric:** Treats solution as a bet to validate, not a commitment
+- **Risk-explicit:** Makes assumptions and risks visible upfront
+- **Executive-friendly:** Comprehensive but structured for C-level review
+- **AI-appropriate:** Especially useful for AI features with high uncertainty
+
+### Anti-Patterns (What This Is NOT)
+- **Not a PRD:** This is strategic framing, not detailed requirements
+- **Not a business case (yet):** It informs the business case but needs validation first
+- **Not a feature list:** Focus on outcomes, not capabilities
+
+### When to Use This
+- Proposing a new AI-powered product or feature
+- Pitching to execs or securing budget/sponsorship
+- Evaluating whether an AI solution is worth pursuing
+- Aligning cross-functional stakeholders (product, engineering, data science, business)
+- After completing initial discovery (you need context to fill this out)
+
+### When NOT to Use This
+- For trivial features (don't over-engineer small tweaks)
+- Before any discovery work (you need user research and problem validation first)
+- As a replacement for experimentation (canvas informs experiments, not vice versa)
+
+---
+
+## Application
+
+Use `template.md` for the full fill-in structure.
+
+### Step 1: Gather Context
+Before filling out the canvas, ensure you have:
+- **Problem understanding:** User research, pain points (reference `skills/problem-statement/SKILL.md`)
+- **Persona clarity:** Who experiences the problem? (reference `skills/proto-persona/SKILL.md`)
+- **Market context:** Competitive landscape, category positioning
+- **Business constraints:** Budget, timelines, strategic priorities
+
+**If missing context:** Run discovery work first. This canvas synthesizes insights—it doesn't create them.
+
+---
+
+### Step 2: Define Outcomes
+
+#### Business Outcome
+What's in it for the business? Use this format:
+- [Direction] [Metric] [Outcome] [Context] [Acceptance Criteria]
+
+```markdown
+## Business Outcome
+- [e.g., "Reduce by 25% the churn of existing customers using our existing product"]
+```
+
+**Example:**
+- "Increase by 15% the monthly recurring revenue from enterprise customers within 12 months"
+
+**Quality checks:**
+- **Measurable:** Can you track this metric?
+- **Time-bound:** Within what timeframe?
+- **Ambitious but realistic:** Not "10x revenue in 1 month"
+
+---
+
+#### Product Outcome
+What's in it for the customer? Use this format:
+- [Direction] [Metric] [Outcome] [Context from persona's POV] [Acceptance Criteria]
+
+```markdown
+## Product Outcome
+- [e.g., "Increase the speed of finding patients when I know the inclusion and exclusion criteria"]
+```
+
+**Example:**
+- "Reduce by 60% the time spent manually processing invoices for small business owners"
+
+**Quality checks:**
+- **Customer-centric:** Written from user perspective ("I," not "we")
+- **Outcome, not feature:** "Reduce time spent" not "Use AI automation"
+
+---
+
+### Step 3: Frame the Problem
+Use the problem framing narrative from `skills/problem-statement/SKILL.md`:
+
+```markdown
+## The Problem Statement
+
+### Problem Statement Narrative
+- [Persona description: 2-3 sentences telling the persona's story from their POV]
+- [Example: "Sarah is a freelance designer managing 10 clients. She spends 8 hours/month manually tracking invoices and chasing late payments. By the time she follows up, some clients have already moved to other designers, costing her revenue and damaging relationships."]
+```
+
+**Quality checks:**
+- **Empathetic:** Does this sound like the user's voice?
+- **Specific:** Not "users want better tools" but "Sarah spends 8 hours/month..."
+- **Validated:** Based on real user research, not assumptions
+
+---
+
+### Step 4: Define the Solution Hypothesis
+
+#### Hypothesis Statement
+Use the epic hypothesis format from `skills/epic-hypothesis/SKILL.md`:
+
+```markdown
+## Solution Hypothesis
+
+### Hypothesis Statement
+**If we** [action or solution on behalf of target persona]
+**for** [target persona]
+**Then we will** [attain or achieve desirable outcome]
+```
+
+**Example:**
+- "If we provide AI-powered invoice reminders that auto-send at optimal times for freelance designers, then we will reduce time spent on payment follow-ups by 70%"
+
+---
+
+#### Tiny Acts of Discovery
+Define lightweight experiments to validate the hypothesis:
+
+```markdown
+### Tiny Acts of Discovery
+**We will test our assumption by:**
+- [Experiment 1: Prototype AI reminder system and test with 5 freelancers]
+- [Experiment 2: A/B test manual vs. AI-timed reminders for 20 users]
+- [Experiment 3: Survey users on perceived value after 2 weeks]
+```
+
+**Quality checks:**
+- **Fast:** Days/weeks, not months
+- **Cheap:** Prototypes, concierge tests, not full builds
+- **Falsifiable:** Could prove you wrong
+
+---
+
+#### Proof-of-Life
+Define validation measures:
+
+```markdown
+### Proof-of-Life
+**We know our hypothesis is valid if within** [timeframe]
+**we observe:**
+- [Quantitative outcome: e.g., "80% of users send reminders via the AI system"]
+- [Qualitative outcome: e.g., "8 out of 10 users report saving 5+ hours/month"]
+```
+
+---
+
+### Step 5: Define Positioning
+Use the positioning statement format from `skills/positioning-statement/SKILL.md`:
+
+```markdown
+## Positioning Statement
+
+### Value Proposition
+**For** [target customer/user persona]
+**that need** [statement of underserved need]
+[product name]
+**is a** [product category]
+**that** [statement of benefit, focusing on outcomes]
+
+### Differentiation Statement
+**Unlike** [primary competitor or competitive arena]
+[product name]
+**provides** [unique differentiation, focusing on outcomes]
+```
+
+---
+
+### Step 6: Document Assumptions & Unknowns
+
+```markdown
+## Assumptions & Unknowns
+- **[Assumption 1]** - [Description, e.g., "We assume users will trust AI-generated reminders"]
+- **[Assumption 2]** - [Description, e.g., "We assume payment timing optimization increases response rates"]
+- **[Unknown 1]** - [Description, e.g., "We don't know if users prefer email or SMS reminders"]
+```
+
+**Quality checks:**
+- **Explicit:** Make hidden assumptions visible
+- **Testable:** Each assumption can be validated via experiments
+
+---
+
+### Step 7: Identify PESTEL Risks
+
+#### Risks to Investigate (High Priority)
+```markdown
+## Issues/Risks to Investigate
+- **Political:** [e.g., "Regulatory changes to AI-generated communications"]
+- **Economic:** [e.g., "Economic downturn reduces willingness to pay for premium features"]
+- **Social:** [e.g., "Users may perceive AI reminders as impersonal or pushy"]
+- **Technological:** [e.g., "AI model accuracy may degrade over time without retraining"]
+- **Environmental:** [e.g., "Energy costs of AI processing"]
+- **Legal:** [e.g., "GDPR compliance for storing customer email patterns"]
+```
+
+---
+
+#### Risks to Monitor (Lower Priority)
+```markdown
+## Issues/Risks to Monitor
+- **Political:** [e.g., "Potential AI regulation in EU markets"]
+- **Economic:** [e.g., "Exchange rate fluctuations affecting international customers"]
+- **Social:** [e.g., "Changing norms around automated communication"]
+- **Technological:** [e.g., "Emerging AI competitors with better models"]
+- **Environmental:** [e.g., "Carbon footprint concerns from stakeholders"]
+- **Legal:** [e.g., "Future data privacy laws"]
+```
+
+---
+
+### Step 8: Justify the Value
+
+```markdown
+## Value Justification
+
+### Is this Valuable?
+- [Absolutely yes / Yes with caveats / No with suggested alternatives / Absolutely NO!]
+
+### Solution Justification
+<!-- Write these to convince C-level executives -->
+We think this is a valuable idea. Here's why:
+1. **[Justification 1]** - [Description, e.g., "Addresses the #1 pain point for our target segment"]
+2. **[Justification 2]** - [Description, e.g., "Differentiates us from competitors who only offer manual reminders"]
+3. **[Justification 3]** - [Description, e.g., "Low technical risk—leverages existing AI infrastructure"]
+```
+
+---
+
+### Step 9: Define Success Metrics
+Use SMART metrics (Specific, Measurable, Attainable, Relevant, Time-Bound):
+
+```markdown
+## Success Metrics
+1. **[Metric 1]** - [e.g., "80% of active users adopt AI reminders within 3 months"]
+2. **[Metric 2]** - [e.g., "Average time spent on payment follow-ups decreases by 50% within 6 months"]
+3. **[Metric 3]** - [e.g., "Net Promoter Score for invoicing feature increases from 6 to 8 within 6 months"]
+```
+
+---
+
+### Step 10: Define Next Steps
+
+```markdown
+## What's Next
+1. **[Next step 1]** - [e.g., "Run 2-week prototype test with 10 beta users"]
+2. **[Next step 2]** - [e.g., "Build lightweight AI model for reminder timing optimization"]
+3. **[Next step 3]** - [e.g., "Conduct legal review of GDPR implications"]
+4. **[Next step 4]** - [e.g., "Present findings to exec team for go/no-go decision"]
+5. **[Next step 5]** - [e.g., "If validated, add to Q2 roadmap"]
+```
+
+---
+
+## Examples
+
+See `examples/sample.md` for a full recommendation canvas example.
+
+Mini example excerpt:
+
+```markdown
+### Business Outcome
+- Increase by 20% MRR from freelance users within 12 months
+
+### Solution Hypothesis
+**If we** provide AI-powered invoice reminders
+**for** freelance designers
+**Then we will** reduce time spent on follow-ups by 70%
+```
+
+## Common Pitfalls
+
+### Pitfall 1: Vague Outcomes
+**Symptom:** "Business outcome: increase revenue. Product outcome: improve UX."
+
+**Consequence:** No measurability or accountability.
+
+**Fix:** Use the outcome formula: [Direction] [Metric] [Outcome] [Context] [Acceptance Criteria]. Be specific.
+
+---
+
+### Pitfall 2: Solution-First Thinking
+**Symptom:** Problem statement is "We need AI-powered X"
+
+**Consequence:** You've jumped to solution without validating the problem.
+
+**Fix:** Frame problem from user perspective. Let the solution hypothesis emerge from validated pain points.
+
+---
+
+### Pitfall 3: Skipping Tiny Acts of Discovery
+**Symptom:** Hypothesis → straight to roadmap, no experiments
+
+**Consequence:** High risk of building the wrong thing.
+
+**Fix:** Define 2-3 lightweight experiments. Test before committing engineering resources.
+
+---
+
+### Pitfall 4: Generic PESTEL Risks
+**Symptom:** "Political: regulations might change"
+
+**Consequence:** Risk analysis is theater, not actionable.
+
+**Fix:** Be specific: "GDPR compliance for storing client email timing data requires legal review."
+
+---
+
+### Pitfall 5: Weak Value Justification
+**Symptom:** "This is valuable because customers will like it"
+
+**Consequence:** Not convincing to execs.
+
+**Fix:** Use data: "Addresses #1 pain point per user research. 20% churn reduction = $500k ARR. Low tech risk."
+
+---
+
+## References
+
+### Related Skills
+- `skills/problem-statement/SKILL.md` — Informs the problem narrative
+- `skills/epic-hypothesis/SKILL.md` — Informs the solution hypothesis structure
+- `skills/positioning-statement/SKILL.md` — Informs positioning section
+- `skills/proto-persona/SKILL.md` — Defines target persona
+- `skills/jobs-to-be-done/SKILL.md` — Informs customer outcomes
+
+### External Frameworks
+- Osterwalder's Value Proposition Canvas — Influences problem/solution framing
+- PESTEL Analysis — Risk assessment framework
+- SMART Goals — Success metrics structure
+
+### Dean's Work
+- AI Recommendation Canvas Template (created for Productside "AI Innovation for Product Managers" class)
+
+### Provenance
+- Adapted from `prompts/recommendation-canvas-template.md` in the `https://github.com/deanpeters/product-manager-prompts` repo.
+
+---
+
+**Skill type:** Component
+**Suggested filename:** `recommendation-canvas.md`
+**Suggested placement:** `/skills/components/`
+**Dependencies:** References `skills/problem-statement/SKILL.md`, `skills/epic-hypothesis/SKILL.md`, `skills/positioning-statement/SKILL.md`, `skills/proto-persona/SKILL.md`, `skills/jobs-to-be-done/SKILL.md`

package/skills/recommendation-canvas/examples/sample.md

@@ -0,0 +1,94 @@
+# Recommendation Canvas Example
+
+## Example: AI-Powered Invoice Reminder System (Good Canvas)
+
+```markdown
+## AI Invoice Reminder Canvas
+
+### Product Name
+- SmartReminders
+
+### Business Outcome
+- Increase by 20% the monthly recurring revenue from freelance users within 12 months by reducing churn caused by payment frustration
+
+### Product Outcome
+- Reduce by 70% the time freelancers spend chasing late payments when using our invoicing platform
+
+### The Problem Statement
+Sarah is a freelance designer managing 10 clients at once. She spends 5+ hours per month manually tracking overdue invoices and sending follow-up emails. By the time she follows up, some clients have already forgotten or moved on, costing her revenue and damaging relationships. She feels anxious and frustrated, wishing she could focus on design instead of admin.
+
+### Solution Hypothesis
+
+**If we** provide AI-powered invoice reminders that auto-send at optimal times
+**for** freelance designers using our invoicing platform
+**Then we will** reduce time spent on payment follow-ups by 70% and increase on-time payment rates by 30%
+
+**Tiny Acts of Discovery:**
+- Prototype AI reminder system and test with 5 freelancers for 2 weeks
+- A/B test manual vs. AI-timed reminders with 20 users
+- Survey users on perceived value and trust in AI-generated messages
+
+**Proof-of-Life:**
+Within 4 weeks, we observe:
+- 80% of test users adopt AI reminders (quantitative)
+- 8 out of 10 users report saving 3+ hours/month (qualitative)
+- On-time payment rate increases by 20% (quantitative)
+
+### Positioning Statement
+
+**For** freelance creative professionals
+**that need** to reduce time spent chasing late payments without damaging client relationships
+SmartReminders
+**is an** AI-powered invoicing automation feature
+**that** automatically sends payment reminders at optimal times, increasing on-time payments by 30%
+
+**Unlike** manual reminder systems or generic email schedulers
+SmartReminders
+**provides** AI-optimized timing based on client behavior patterns, maximizing response rates without appearing pushy
+
+### Assumptions & Unknowns
+- **Assumption 1:** Users will trust AI to send messages on their behalf
+- **Assumption 2:** Optimal reminder timing improves payment rates
+- **Unknown 1:** Whether users prefer email, SMS, or in-app reminders
+- **Unknown 2:** How to handle clients who never respond to reminders
+
+### Issues/Risks to Investigate
+- **Political:** N/A (low risk)
+- **Economic:** Recession may reduce willingness to pay for premium features
+- **Social:** Users may perceive AI reminders as impersonal or spammy
+- **Technological:** AI model accuracy may degrade without retraining
+- **Environmental:** Minimal (low energy costs)
+- **Legal:** GDPR compliance for storing client email patterns and timing data
+
+### Issues/Risks to Monitor
+- **Political:** Future AI regulation
+- **Economic:** Currency fluctuations for international users
+- **Social:** Changing norms around automated business communication
+- **Technological:** Competitor AI models
+- **Environmental:** Carbon footprint concerns
+- **Legal:** Evolving data privacy laws
+
+### Value Justification
+
+**Is this Valuable?**
+- Absolutely yes
+
+**Solution Justification:**
+1. **Addresses top pain point:** Payment follow-ups are the #1 complaint from freelance users (per user research)
+2. **Differentiates from competitors:** Competitors offer manual reminders; we offer AI-optimized timing
+3. **Low technical risk:** Leverages existing AI infrastructure and user behavior data
+4. **High business impact:** Reducing churn by 20% = $500k ARR
+
+### Success Metrics
+1. **Adoption:** 75% of active invoicing users enable AI reminders within 3 months
+2. **Time savings:** Average time spent on payment follow-ups decreases by 60% within 6 months
+3. **Payment rates:** On-time payment rate increases from 50% to 65% within 6 months
+4. **NPS:** Net Promoter Score for invoicing feature increases from 6 to 8
+
+### What's Next
+1. **Run prototype test:** 2-week test with 10 beta users
+2. **Build lightweight AI model:** Optimize reminder timing based on client response patterns
+3. **Legal review:** GDPR compliance check
+4. **Present to execs:** Go/no-go decision by end of Q1
+5. **If validated:** Add to Q2 roadmap as high-priority feature
+```

package/skills/recommendation-canvas/template.md

@@ -0,0 +1,86 @@
+# Recommendation Canvas Template
+
+Use this template to produce a complete AI recommendation canvas.
+
+## Provenance
+Adapted from `prompts/recommendation-canvas-template.md` in the `https://github.com/deanpeters/product-manager-prompts` repo.
+
+## Template
+```markdown
+## AI Recommendation Canvas
+
+### Product Name
+- [Name of the AI product or service]
+
+### Business Outcome
+- [Direction][Metric][Outcome][Context][Acceptance criteria]
+
+### Product Outcome
+- [Direction][Metric][Outcome][Context][Acceptance criteria]
+
+### The Problem Statement
+- [2-3 sentence narrative from the persona's POV]
+
+### Solution Hypothesis
+**If we** [action or solution]
+**for** [target persona]
+**Then we will** [desirable outcome]
+
+**Tiny Acts of Discovery:**
+- [Experiment 1]
+- [Experiment 2]
+- [Add more as needed]
+
+**Proof-of-Life:**
+Within [timeframe], we observe:
+- [Quantitative outcome]
+- [Qualitative outcome]
+
+### Positioning Statement
+**For** [target customer/persona]
+**that need** [underserved need]
+[product name]
+**is a** [product category]
+**that** [benefit statement]
+
+**Unlike** [primary competitor or alternative]
+[product name]
+**provides** [unique differentiation]
+
+### Assumptions & Unknowns
+- **[Assumption/Unknown 1]** - [Description]
+- **[Assumption/Unknown 2]** - [Description]
+
+### Issues/Risks to Investigate (PESTEL)
+- **Political:** [Risk]
+- **Economic:** [Risk]
+- **Social:** [Risk]
+- **Technological:** [Risk]
+- **Environmental:** [Risk]
+- **Legal:** [Risk]
+
+### Issues/Risks to Monitor (PESTEL)
+- **Political:** [Risk]
+- **Economic:** [Risk]
+- **Social:** [Risk]
+- **Technological:** [Risk]
+- **Environmental:** [Risk]
+- **Legal:** [Risk]
+
+### Value Justification
+**Is this Valuable?** [Absolutely yes / Yes with caveats / No]
+
+**Solution Justification:**
+1. **[Justification 1]** - [Description]
+2. **[Justification 2]** - [Description]
+
+### Success Metrics
+1. **[Metric 1]** - [Description]
+2. **[Metric 2]** - [Description]
+3. **[Metric 3]** - [Description]
+
+### What's Next
+1. **[Next step 1]** - [Description]
+2. **[Next step 2]** - [Description]
+3. **[Next step 3]** - [Description]
+```