blueprint

Name: blueprint
Availability: InStock
Author: juicesharp

Decompose features into vertical slices and generate phased implementation plans.

581|102|Updated Apr 18, 2026

Search Tags:#planning #code-generation #phase-based #feature-design #engineering-workflow #vertical-slices

Ready to run

npx skills add https://github.com/juicesharp/rpiv-mono --skill blueprint-juicesharp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/blueprint
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill blueprint-juicesharp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex software features by decomposing them into vertical slices and generating an implement-ready phased plan to reduce risk and speed delivery.

Core Features & Use Cases

Vertical-slice decomposition: break a feature into independent, end-to-end slices.
Phase-based planning: produce a structured artifact that guides implementation (slices, wiring, and milestones).
Decision traceability: capture decisions and dependencies to support iterative development and audits.

Quick Start

Provide a research artifact path to begin planning a feature, and the skill will generate phased, implement-ready slices

Frequently Asked Questions about blueprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan complex software features using vertical slices?▼

To plan feature development, you provide a research artifact path. The skill then decomposes the feature into vertical slices, aligns with existing code patterns, and produces a stepwise execution plan with traceable decisions and phase-based delivery checkpoints.

What is phase-based planning for feature design and delivery?▼

Phase-based planning produces a structured artifact that guides implementation through slices, wiring, and milestones. It captures decisions and dependencies to support iterative development, audits, and structured delivery checkpoints.

What's the best way to decompose a feature into implement-ready artifacts?▼

The best way is to orchestrate end-to-end feature development by breaking it into independent vertical slices. This generates implement-ready artifacts with traceable decisions and dependencies, ensuring a stepwise execution plan that reduces delivery risk.

Do I need a research artifact to start engineering workflow planning?▼

Yes, you need to provide a research artifact path to begin planning a feature. The skill uses this input to generate phased, implement-ready slices tailored to your software engineering project.

How does decision traceability work in an engineering workflow plan?▼

Decision traceability captures decisions and dependencies within the phased plan. This supports iterative development and audits by maintaining a clear record of how the vertical slices and milestones were designed.