skills.rest
michael-menard
michael-menardCOMMUNITY
Explore all skills by this author →
GitHub

review-draft-story

Coordinate parallel PM, UX, and SM reviews to validate draft stories.

Updated Aug 27, 2026
Search Tags:#automation#UX#story#review#scrum#PM#go-no-go
One-click install
npx skills add https://github.com/michael-menard/monorepo --skill review-draft-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-draft-story
Source: https://github.com/michael-menard/monorepo/tree/main/.claude/skills/review-draft-story
Command: npx skills add https://github.com/michael-menard/monorepo --skill review-draft-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the review process for draft stories by orchestrating parallel input from product, UX, and Scrum Specialist reviewers, ensuring a comprehensive pre-implementation assessment.

Core Features & Use Cases

  • Parallel specialist reviews: PM, UX, and SM analyze a story simultaneously to reduce cycle time.
  • Unified assessment: Aggregates findings into a final ready/not-ready decision with actionable fixes.
  • Flexible execution: Supports quick reviews, focus areas, and reviewer skip options to adapt to context.
  • Collaboration & traceability: Consolidates feedback into a single concise report for stakeholders.

Quick Start

Run /review-draft-story 2002 to start a draft review. Optional: /review-draft-story 2002 --quick for a lightweight review. Use path: /review-draft-story docs/stories/epic-6-wishlist/wish-2002-add-item-flow.md. Focus options:

  • /review-draft-story 2002 --focus=ux Skip reviewer: /review-draft-story 2002 --skip-pm

Frequently Asked Questions about review-draft-story

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

FAQPage Schema
How do I coordinate parallel stakeholder reviews for a draft story?▼

To coordinate parallel stakeholder reviews, run a draft story review that simultaneously analyzes input from PM, UX, and SM perspectives, aggregating findings into a single consolidated report with actionable fixes.

When do I need a GO/NO-GO decision before story development?▼

You need a GO/NO-GO decision before development to validate early-stage story drafts across product, UX, and Scrum perspectives, ensuring comprehensive pre-implementation assessment and reducing cycle time.

How do I run a quick review on a specific story file path?▼

Run a quick review by providing the story file path or ID with the --quick flag, executing a lightweight parallel assessment that outputs YAML blocks of issues for rapid consolidation.

Can I focus a draft story review on just the UX perspective?▼

Yes, you can focus a draft story review on the UX perspective by using the --focus=ux flag, or limit scope by skipping reviewers like PM with the --skip-pm option to adapt to specific context.

What is the best way to consolidate feedback from multiple specialist reviewers?▼

The best way to consolidate specialist feedback is to run a parallel review that aggregates PM, UX, and SM findings into a unified assessment, outputting a concise report with a final ready or not-ready decision.

Does the draft story review process require specific dependencies?▼

No specific dependencies are required to run the draft story review, which loads context directly from the story file and references to validate drafts and output YAML blocks of issues.

Related Skills

Explore More Product & Management Skills→
core-wrkcore-wrk

pitch-deck-builder

Generate a pitch deck outline and narrative with speaker notes from project context files.

Official
Intermediate
pillippillip
11

bizanalysis

Analyze product idea business viability and generate a go/no-go decision for sprint planning.

Community
Advanced
zhizhunbaozhizhunbao

dev-scrum

Generate sprint backlogs, user stories, and task breakdowns from PRD requirements.

Community
Advanced
krhrtkykrhrtky

principle-guide

Create and apply reusable principles to automate recurring decisions.

Community
Basic