skills.rest
juicesharp
juicesharpCOMMUNITY
Explore all skills by this author →
GitHub

design

Coordinate end-to-end feature design using vertical-slice decomposition and developer micro-checkpoints.

581|102|Updated Apr 18, 2026
Search Tags:#design#architecture#checkpoints#development-process#feature-design#vertical-slices
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill design-juicesharp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/design
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill design-juicesharp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative vertical-slice design coordinates feature exploration and planning for multi-file changes, generating a living artifact that guides subsequent plan, design, and implementation phases.

Core Features & Use Cases

  • Decompose complex features into vertical slices to align architecture, code, and tests across layers.
  • Produce design artifacts and documentation stored under thoughts/shared/designs/ for traceability and handoff.
  • Require a research artifact from discover/research or a solutions artifact from explore as input seeds to drive depth and decisions.

Quick Start

Provide a research artifact path to begin iterative design of a feature using vertical slices.

Frequently Asked Questions about design

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

FAQPage Schema
How do I plan complex multi-file feature design across modules and teams?▼

Complex multi-file feature design is planned by decomposing the work into vertical slices and developer micro-checkpoints, generating a living design artifact that aligns architecture, code, and tests across layers.

What is vertical-slice decomposition for feature development?▼

Vertical-slice decomposition is a feature development technique that breaks complex changes into iterative slices, coordinating end-to-end architecture and tests to guide subsequent implementation phases.

Do I need a research artifact to start iterative feature design?▼

Yes, iterative feature design requires a research artifact from a prior discovery phase or a solutions artifact as an input seed to drive depth, decisions, and slice-based generation.

How do I coordinate architecture and code changes for a new feature?▼

Architecture and code changes are coordinated by producing a living design artifact with decision-logging and slice-based generation stored under a shared designs directory for traceability and team handoff.

When should I use vertical slices for software architecture planning?▼

Vertical slices should be used for software architecture planning when tackling complex multi-file changes across modules and teams that require iterative exploration and a structured design artifact.

What is the best way to document feature design for team handoff?▼

The best way to document feature design for handoff is to maintain a living design artifact with frontmatter and decision-logging in a shared designs directory, ensuring traceability across implementation phases.

Related Skills

Explore More Software Engineering Skills→
ARAVINDAN20ARAVINDAN20
4

experiment-design

Plan experimental designs with baselines, datasets, hyperparameters, and evaluation metrics.

Community
Advanced
BrightBlockBrightBlock
2

create_plan_nt

Generate implementation plans with phases and success criteria for non-standard project structures.

Official
Advanced
dayvidphamdayvidpham
2

impl-slice

Coordinate vertical slice planning, worker assignment, and progress tracking.

Community
Advanced
juicesharpjuicesharp
581

blueprint

Decompose features into vertical slices and generate phased implementation plans.

Community
Advanced