refinement

Decompose product requirement briefs into ordered user-story specifications and implementation plans.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Jeff-Stapleton/dotclaude --skill refinement-jeff-stapleton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refinement
Source: https://github.com/Jeff-Stapleton/dotclaude/tree/main/.claude/skills/refinement
Command: npx skills add https://github.com/Jeff-Stapleton/dotclaude --skill refinement-jeff-stapleton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms high-level product requirements and technical designs into detailed, actionable user stories, ensuring clarity and alignment for development teams.

Core Features & Use Cases

  • Requirement Decomposition: Breaks down complex briefs into granular user stories.
  • Dependency Mapping: Orders stories based on dependencies and value delivery.
  • Implementation Planning: Generates a clear roadmap for development.
  • Use Case: A product manager provides a new feature brief. This Skill analyzes it, along with technical architecture documents and Storybook designs, to produce a prioritized list of user stories, each with clear acceptance criteria and technical specifications, ready for the engineering team.

Quick Start

Use the refinement skill to decompose the product requirement brief located at /path/to/product-requirement-brief.md.

Frequently Asked Questions about refinement

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

FAQPage Schema
How do I decompose product requirement briefs into actionable user stories?

Decomposing product requirement briefs involves analyzing them with technical architectures and Storybook designs to produce ordered user-story specifications. The process includes ingestion, spec generation, optional dual-agent reviews, and final implementation plan creation.

What is the best way to generate an implementation plan from a technical specification?

The best way to generate an implementation plan from a technical specification is to use multi-phase execution that maps dependencies and orders stories by value delivery, resulting in a clear development roadmap.

How do I manage context window limits when processing large technical architectures?

Managing context window limits for large technical architectures requires built-in context window management and resumability. This approach handles large inputs by processing them across multiple execution phases without losing prior decomposition progress.

Does this requirement decomposition approach work with Storybook designs?

Yes, requirement decomposition works directly with Storybook designs. The Skill ingests Storybook designs alongside product requirement briefs and technical architectures to generate granular user stories with technical specifications and acceptance criteria.

When should I use dual-agent reviews for user story generation?

You should use dual-agent reviews for user story generation when processing complex requirement briefs that demand high alignment. This optional review phase validates the generated technical specifications and acceptance criteria before final implementation plan creation.