pm-requirement-flow

Convert vague requirements into actionable SPECs for Claude Code.

Updated Apr 12, 2026

Search Tags:#workflow #requirements #dispatch #spec #pm #acceptance #agency-agents

Ready to run

npx skills add https://github.com/yiguoguo/yi-openclaw-skills --skill pm-requirement-flow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-requirement-flow
Source: https://github.com/yiguoguo/yi-openclaw-skills/tree/main/pm-requirement-flow
Command: npx skills add https://github.com/yiguoguo/yi-openclaw-skills --skill pm-requirement-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PM projects often stall due to unclear requirements and fragmented handoffs. This Skill guides you through a structured end-to-end workflow to clarify context, capture user needs, and convert them into a concrete SPEC, then dispatch work and track acceptance with measurable criteria.

Core Features & Use Cases

Structured SPEC creation from user prompts and project context.
End-to-end PM workflow: clarify requirements, write SPEC, dispatch, and verify acceptance.
Integration with agency-agents for role-based tasking and collaboration.
Task-tracker driven release with clear success criteria and traceability.

Quick Start

Draft a SPEC from a vague request and dispatch it to Claude Code for execution using the defined PM workflow.

Frequently Asked Questions about pm-requirement-flow

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

FAQPage Schema

How do I turn vague product requirements into actionable SPEC documents?▼

To turn vague product requirements into actionable SPEC documents, you need a structured PM workflow that clarifies context, captures user needs, and converts them into concrete specifications with measurable acceptance criteria. This ensures traceable and testable delivery across collaborative teams.

What is the best way to manage requirement dispatch and acceptance verification in PM workflows?▼

Requirement dispatch and acceptance verification in PM workflows are managed through a task-tracker driven release process. This approach enforces structured inputs and explicit acceptance criteria, ensuring that dispatched work remains traceable and testable throughout the delivery lifecycle.

Can I use agency-agents integration for role-based tasking in requirement management?▼

Yes, you can use agency-agents integration for role-based tasking within requirement management. This integration supports collaborative teams by converting clarified SPEC documents into dispatched tasks for Claude Code, enabling structured execution and verification.

How do I create structured SPECs from user prompts and project context?▼

Creating structured SPECs from user prompts and project context requires enforcing structured inputs within a PM workflow. The process captures vague needs and project context, drafting a concrete SPEC that defines explicit success criteria for downstream dispatch and acceptance.

Why do PM projects stall during handoffs and how to prevent it?▼

PM projects stall during handoffs due to unclear requirements and fragmented communication between teams. You can prevent this by implementing an end-to-end PM workflow that enforces structured inputs, ensuring every requirement is converted into a traceable SPEC with measurable acceptance criteria.

Does this PM workflow support end-to-end delivery from requirement clarification to acceptance?▼

Yes, this PM workflow supports end-to-end delivery from requirement clarification to acceptance. It guides teams through the entire process: clarifying vague needs, drafting a SPEC, dispatching work to Claude Code, and tracking acceptance with measurable success criteria.