Skip to content

Release Notes - v0.8.0

Release Date: 2026-02-08

Overview

This release adds markdown rendering for 8 extended PRD sections that were previously defined in the schema but not rendered. It also introduces structured NonGoals and SuccessMetrics fields with full rendering and completeness scoring support, plus configurable section ordering with PRD type templates.

New Features

Configurable Section Ordering

Control the order of sections in generated markdown with PRD type templates or custom ordering:

PRD Type Templates:

Type Description Early Sections
strategy Context-first ordering CurrentState, Problem, Market
feature User-needs-first ordering Problem, Personas, UserStories
technical Architecture-focused ordering TechArchitecture, SecurityModel

CLI Usage:

# Use a PRD type template
splan req prd generate input.json --type=strategy

# Custom section order (partial list - remaining sections appended)
splan req prd generate input.json --order=executiveSummary,problem,solution

# List available section IDs
splan req prd list-sections

JSON Configuration:

{
  "metadata": {
    "prdType": "strategy",
    "sectionOrder": ["executiveSummary", "problem", "solution"]
  }
}

Extended Section Rendering (ENH-001 to ENH-006)

Six existing data model fields now have full markdown rendering:

1. Problem Definition

Renders problem statement, user impact, evidence table, root causes, and affected segments:

## Problem Definition

### Problem Statement
Users struggle to find relevant documents...

**Confidence:** 85%

### Evidence
| Type | Source | Summary | Sample Size | Strength | Date |
|------|--------|---------|-------------|----------|------|
| survey | Q4 User Survey | 73% of users report difficulty | 500 | high | 2024-01 |

### Root Causes
- Poor search algorithm
- Lack of metadata

### Affected Segments
- Enterprise users
- Remote workers

2. Market Analysis

Renders alternatives table with strengths/weaknesses, differentiation, and market risks:

## Market Analysis

### Alternatives
| ID | Name | Type | Description | Why Not Chosen |
|----|------|------|-------------|----------------|
| ALT-001 | Competitor A | competitor | Market leader | Too expensive |

#### Competitor A
**Strengths:**
- Brand recognition
- Large user base

**Weaknesses:**
- Expensive
- Complex

### Differentiation
- AI-powered search
- Better mobile experience

### Market Risks
- Market saturation

3. Solution

Renders solution options table with selection indicator, benefits/tradeoffs/risks, and rationale:

## Solution

### Solution Options
| ID | Name | Description | Effort | Selected |
|----|------|-------------|--------|----------|
| SOL-001 | Build In-House | Custom solution | 6 months | ✅ Selected |
| SOL-002 | Buy Off-the-Shelf | Commercial solution | 2 months | |

#### Build In-House ✅ *Selected*
**Benefits:**
- Full control
- Custom features

**Tradeoffs:**
- Higher cost
- Longer timeline

### Solution Rationale
Custom solution provides better long-term value.

**Confidence:** 75%

Supports --text-icons flag for PDF compatibility ([*] Selected instead of ✅ Selected).

4. Decisions

Renders decision records table with alternatives considered:

## Decisions

| ID | Decision | Rationale | Status | Date | Made By |
|----|----------|-----------|--------|------|---------|
| DEC-001 | Use PostgreSQL | Better JSON support | accepted | 2024-01-15 | Architecture Team |

**DEC-001 - Alternatives Considered:**
- MySQL
- MongoDB

5. Reviews

Renders review decision badge, quality scores, blockers, and revision triggers:

## Reviews

### Review Board Summary
PRD meets quality standards with minor issues.

**Decision:** ✅ Approved

### Quality Scores
| Dimension | Score |
|-----------|-------|
| Problem Definition | 8.5 |
| User Understanding | 9.0 |
| **Overall Score** | **8.1** |

### Blockers
- **BLK-001** (Security): Missing threat model

### Revision Triggers
| Issue ID | Category | Severity | Description | Recommended Owner |
|----------|----------|----------|-------------|-------------------|
| REV-001 | UX | minor | Need more wireframes | Design Team |

Supports --text-icons flag ([APPROVED] instead of ✅ Approved).

6. Revision History

Renders version history table with trigger and change summary:

## Revision History

| Version | Date | Author | Trigger | Changes |
|---------|------|--------|---------|---------|
| 1.0 | 2024-01-10 | John Doe | initial | Initial draft; Added personas |
| 1.1 | 2024-01-20 | Jane Doe | review | Updated requirements |

New Data Model Fields (ENH-007 to ENH-008)

Two new fields added to the PRD Document type:

7. NonGoals

Structured non-goals with rationale (more detailed than outOfScope):

{
  "nonGoals": [
    {
      "id": "NG-001",
      "title": "Mobile App",
      "description": "Native mobile application",
      "rationale": "Focus on web first",
      "futurePhase": "Phase 2"
    }
  ]
}

Rendered as:

## Non-Goals

| ID | Title | Description | Rationale | Future Phase |
|----|-------|-------------|-----------|--------------|
| NG-001 | Mobile App | Native mobile application | Focus on web first | Phase 2 |

8. SuccessMetrics

Structured success metrics organized by type:

{
  "successMetrics": {
    "northStar": [
      {
        "id": "NS-001",
        "name": "User Retention",
        "description": "Monthly active users returning",
        "baseline": "65%",
        "target": "80%",
        "measurementMethod": "Analytics dashboard"
      }
    ],
    "supporting": [
      {
        "id": "SUP-001",
        "name": "NPS Score",
        "target": "60"
      }
    ],
    "guardrail": [
      {
        "id": "GR-001",
        "name": "Page Load Time",
        "target": "<3s"
      }
    ]
  }
}

Rendered as:

## Success Metrics

### North Star Metrics
*Primary metrics that define success.*

| ID | Name | Description | Baseline | Target | Measurement Method |
|----|------|-------------|----------|--------|-------------------|
| NS-001 | User Retention | Monthly active users returning | 65% | 80% | Analytics dashboard |

### Supporting Metrics
*Metrics that support the north star metrics.*
...

### Guardrail Metrics
*Metrics that should not degrade.*
...

Completeness Scoring

All 8 new sections contribute to the PRD completeness score:

Section Max Points What's Checked
Problem Definition 5 Statement, user impact, evidence, root causes
Market Analysis 5 Alternatives, differentiation, market risks
Solution 5 Options, selected solution, rationale, confidence
Decisions 5 Record count, rationale completeness
Reviews 5 Decision, quality scores, blockers
Revision History 5 Revision count, change descriptions
Non-Goals 5 Non-goal count, rationale completeness
Success Metrics 5 North star (required), supporting, guardrail

Optional sections total increased from 8 to 16.

Table of Contents

All new sections are automatically added to the generated Table of Contents when present.

Installation

Homebrew (macOS/Linux)

brew upgrade grokify/tap/splan

Go Install

go install github.com/grokify/structured-plan/cmd/splan@v0.8.0

Go Module

go get github.com/grokify/structured-plan@v0.8.0

Full Changelog

See CHANGELOG.md for complete details.