Use when breaking down milestones, epics, or product-level goals into multiple feature-sized pieces for vrau workflows. Use BEFORE starting any vrau:start when the scope is larger than a single feature.
Breaks large goals into feature-sized pieces for vrau workflows.
/plugin marketplace add mguilarducci/vrau/plugin install vrau@vrau-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Break big goals (milestones, epics, products) into feature-sized pieces. Each piece becomes input for a separate vrau:start workflow.
Output WHAT to build, not HOW. Save implementation details for the brainstorm phase of each piece.
Use this skill when the goal is larger than a single feature:
Skip decomposition and go directly to vrau:start when:
Signs you're over-decomposing:
When in doubt: Try vrau:start first. If brainstorming reveals the scope is too large, then come back and decompose.
digraph decomposition {
"Receive big goal" -> "Understand context";
"Understand context" -> "Ask clarifying questions";
"Ask clarifying questions" -> "Explore decomposition approaches";
"Explore decomposition approaches" -> "Present 2-3 approaches";
"Present 2-3 approaches" -> "User selects approach";
"User selects approach" -> "Write piece files";
"Write piece files" -> "Present summary with next steps";
}
Before decomposing, understand:
Read relevant files, docs, recent commits. Don't assume.
One question at a time. Must clarify:
Always present 2-3 different ways to slice the milestone:
| Approach | Description | Pieces | Trade-off |
|---|---|---|---|
| MVP-first | Minimal viable, then enhance | 3-4 | Fast value, may refactor |
| Layer-by-layer | Foundation → Core → Polish | 5-7 | Clean architecture, slower value |
| User-journey | Slice by user workflow | 4-6 | User-focused, may have deps |
Lead with your recommendation and why.
Target 3-7 pieces. More than 7 = probably wrong granularity.
Write to: docs/decomposition/YYYY-MM-DD-<milestone-name>/
File naming: <descriptive-name>.md (NOT numbered: 01-, 02-)
Each file MUST include:
# <Piece Title>
## Milestone Context
<Copy the overall milestone goal here - makes file standalone>
## This Piece
<2-3 sentence description of WHAT this piece delivers>
## Goals
- <User-visible outcome 1>
- <User-visible outcome 2>
## Constraints
- <Hard constraint 1>
- <Hard constraint 2>
## Dependencies
- Blocked by: <piece-name> (if any)
- Blocks: <piece-name> (if any)
- Can parallelize with: <piece-name> (if any)
## Out of Scope
<What this piece explicitly does NOT include>
Create _overview.md with:
These belong in vrau:brainstorm, not here:
If you're writing code or APIs, STOP. You're doing brainstorming, not decomposition.
| You're doing this | Do this instead |
|---|---|
| Writing API examples | Delete them. Just describe the goal. |
| More than 7 pieces | Combine related pieces or split milestone |
| Numbered filenames (01-*) | Use descriptive names |
| Skipping clarifying questions | Ask about MVP, timeline, constraints |
| Single decomposition approach | Present 2-3 options |
| Pieces reference each other by number | Use piece names, include milestone context |
Present the pieces and ask:
Ready to start the first piece?
→ Run vrau:start with <recommended-first-piece>
User will run vrau:start multiple times, once per piece.
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.