blueprint-derive-planslisted

# /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 docs/blueprint -maxdepth 1 -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 "DE