product-requirements

Transform Canvas strategy into structured product requirements and user stories.

37|5|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/BellaBe/lean-os --skill product-requirements-bellabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-requirements
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/product-requirements
Command: npx skills add https://github.com/BellaBe/lean-os --skill product-requirements-bellabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert Canvas strategy into product requirements, user stories, and backlog.

Core Features & Use Cases

  • Context extraction: from 01-context, 05-problem, 09-solution
  • User story map: create walking skeleton
  • PRD generation: optional documentation

Quick Start

Provide Canvas; returns a structured set of requirements.

Frequently Asked Questions about product-requirements

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

FAQPage Schema
How do I convert a Canvas strategy into product requirements and user stories?

Transform Canvas strategy into structured product requirements by extracting context from Canvas sections, generating a user story map with walking skeleton, composing detailed user stories with acceptance criteria, and delivering a complete PRD for feature definition and backlog creation across product teams.

What Canvas sections do I need to provide for PRD generation?

Supply Canvas sections covering context, problem statement, target segments, solution approach, and assumptions. The Skill reads these sections to extract strategic context and generate structured requirements, user story maps, and detailed product documentation.

Can I use this to create a user story map from Canvas?

Yes. The Skill creates a user story map and walking skeleton directly from your Canvas strategy, organizing requirements into actionable user stories with acceptance criteria for backlog creation and sprint planning.

What's the difference between using Canvas versus writing requirements directly?

Canvas captures strategic context—problem, segments, solution, assumptions—which the Skill transforms into structured requirements. This approach ensures requirements remain grounded in strategy and maintains traceability between business decisions and product specifications.

Do I need a complete Canvas to generate requirements?

The Skill reads core Canvas sections: context, problem, segments, solution, and assumptions. A complete Canvas provides richer context, but the Skill extracts and structures whatever strategic content you supply into coherent product requirements and user stories.

What output formats does this Skill generate?

The Skill delivers a user story map with walking skeleton, detailed user stories with acceptance criteria organized by segments, and an optional PRD document—all structured for backlog management and product team alignment.