pm

Converts operational requirements into user stories, acceptance criteria, and technical task plans.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/levori119/skyboard --skill pm-levori119
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm
Source: https://github.com/levori119/skyboard/tree/main/.claude/skills/pm
Command: npx skills add https://github.com/levori119/skyboard --skill pm-levori119

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a raw operational idea into a buildable plan is slow and error-prone: requirements stay vague, existing components get rebuilt, and edge cases surface only after code is written. This Skill structures that discovery phase for the SKY-KING air-traffic control desk application before any code is touched. ## Core Features & Use Cases - Structured Planning Output: Produces a user story, measurable acceptance criteria, station impact table (CTRL/TWR), shared-component analysis, ordered technical tasks with time estimates, and event-log requirements. - DRY Enforcement: Scans existing components and API routes before recommending anything new, preventing duplicate work. - Operational Benchmarking: Applies the physical-strip-board test to every feature, asking whether the digital action is faster than the physical workflow it replaces. - Use Case: A controller requests a new field for logging runway status. The Skill reads the project context, checks for existing components, and outputs a complete story with acceptance criteria and a sequenced task list ready for implementation. ## Quick Start Ask the assistant to act as the SKY-KING product manager and turn your feature idea into a user story with acceptance criteria and technical tasks.

Frequently Asked Questions about pm

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

FAQPage Schema
How do I turn a feature idea into user stories and acceptance criteria?▼

Describe the operational need and the Skill produces a structured user story, numbered measurable acceptance criteria, and an ordered technical task list with rough time estimates. It asks one focused clarifying question if information is missing.

What does a product manager skill check before planning a feature?▼

It reads the project context file, scans existing components and API routes for reuse opportunities, and benchmarks the feature against the physical strip-board workflow it replaces. Only then does it output the plan.

Does this skill write code during the planning phase?▼

No, the Skill explicitly forbids writing code at this stage. It only produces planning artifacts: user stories, acceptance criteria, station impact tables, shared-component analysis, and technical tasks.

How does the skill handle features affecting multiple user stations?▼

It generates a station impact table marking whether each station (flight controller CTRL, tower supervisor TWR) is affected, plus a shared-components section listing which screens change if a common component is modified.

When should a feature be split into multiple user stories?▼

The Skill recommends splitting when a feature is too complex to deliver as one unit. It evaluates complexity during planning and suggests dividing the work into two separate stories with independent acceptance criteria.