shape

Shape vague backlog items into a context packet with goals and constraints.

2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/misty-step/volume --skill shape-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/shape
Command: npx skills add https://github.com/misty-step/volume --skill shape-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Shape a raw idea into a concrete, buildable context packet that guides product and engineering exploration, reducing ambiguity and streamlining alignment.

Core Features & Use Cases

  • Transforms vague backlog items, user prompts, or incident notes into a defined shaping frame with goals, constraints, and success criteria.
  • Produces a breadboarded context packet and an executable plan to drive design, evaluation, and implementation.
  • Supports collaboration across product and engineering by providing a single artifact that can be referenced during /implement and planning sessions.

Quick Start

Shape a backlog item or idea into a concrete context packet that can be immediately used to drive design and planning.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I turn vague backlog items into defined requirements for planning?

To turn vague backlog items into defined requirements, you can apply a shaping process that translates raw ideas into a concrete context packet. This packet defines specific goals, non-goals, and constraints to streamline product and engineering alignment.

What is a context packet and when do I need one for product design?

A context packet is a single artifact that encapsulates goals, non-goals, and constraints for a feature. You need one during product design to reduce ambiguity, guide evaluation, and provide an executable plan ready for implementation.

How do I shape user stories and incident notes into an executable context?

You can shape user stories and incident notes into an executable context by applying a shaping frame to diverse inputs. This process breadboards the raw information into defined outcomes and constraints that guide implementation planning.

What's the best way to align engineering and product teams before implementation?

The best way to align engineering and product teams is generating a single breadboarded context packet that defines outcomes and constraints. This shared artifact can be referenced during planning sessions to ensure collaborative alignment.

Does the shaping process support direct execution with implementation tools?

Yes, the shaping process produces an executable context specifically designed to be ready for implementation. The generated context packet directly guides design and evaluation, making it immediately usable for execution.

What are the limitations of using a context packet for design exploration?

A context packet limits design exploration by strictly defining non-goals and constraints alongside desired outcomes. While this reduces ambiguity and streamlines alignment, it intentionally bounds the scope to ensure focused implementation planning.