blueprint-derive-plans

created	"2026-01-15T00:00:00.000Z"
modified	"2026-06-18T00:00:00.000Z"
reviewed	"2026-05-29T00:00:00.000Z"
description	Derive PRDs, ADRs, PRPs from git history, docs, and codebase. Use when onboarding a project to blueprint, generating a PRD or ADRs retroactively, or extracting features from conventional commits.
args	[--quick] [--since DATE]
argument-hint	--quick for fast scan, --since 2024-01-01 for date range
allowed-tools	Read, Write, Glob, Grep, Bash, AskUserQuestion, Task
model	opus
name	blueprint-derive-plans

/blueprint:derive-plans

Retroactively generate Blueprint documentation (PRDs, ADRs, PRPs) from an existing established project by analyzing git history, codebase structure, and existing documentation.

Use case: Onboarding established projects into the Blueprint Development system when PRD/ADR/PRP documents don't exist but the project has implementation history.

When to Use This Skill

Use this skill when...	Use alternative when...
Project has git history but no PRDs/ADRs/PRPs	Starting a brand new project with no history
Onboarding an established project to Blueprint	Creating a fresh PRD from scratch with user guidance
Need to extract features from commit history	Project lacks conventional commits and clear history
Want to document architecture decisions retroactively	Decisions are already fully documented

Context

• Git repository: !git rev-parse --git-dir
• Blueprint initialized: !find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'manifest.json' -type f
• Total commits: !git rev-list --count HEAD
• First commit: !git log --reverse --format=%ai --max-count=1
• Latest commit: !git log --max-count=1 --format=%ai
• Project type: !find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' -o -name 'pom.xml' \) -type f -print -quit
• Documentation files: !find . -maxdepth 2 \( -name "README.md" -o -name "ARCHITECTURE.md" -o -name "DESIGN.md" \)

Parameters

Parse these from $ARGUMENTS:

• --quick: Fast scan (last 50 commits only)
• --since DATE: Analyze commits from specific date (e.g., --since 2024-01-01)

Default behavior without flags: Standard analysis (last 200 commits with scope estimation).

For detailed templates, manifest format, and report examples, see REFERENCE.md.

Execution

Execute this retroactive documentation generation workflow:

Step 1: Verify prerequisites

Check context values above:

1. If git repository = "NO" → Error: "This directory is not a git repository. Run from project root."